grass.pygrass: Improve exception handling in Info.open (#1555)

[Viech]

No description provided.

[ninsbl]

Bumping up milestone as 8.0.1 is due in two days, while this has not been part of RC1 and there has not been activity for some time.

[wenzeslaus]

After consulting Python documentation, I found one more issue here.

The rest of the code seems to be ready to be merged.

I merged main branch here to resolve conflict with new code on main (only a context line changed).

[wenzeslaus]

All right, this can be merged as is. (CI is still running now.)

@Viech Two questions:

1. You are using % formatting, but in this context .format() or f-string would be more appropriate with current Python. Any reason for that?

2. Your error messages are not translatable (not marked with _(...), .format() or % are then needed, not f-string). Is that intentional? Python does not translate its error messages, but in GRASS we generally do, although for programming-only messages it is permissible not to translate (most of the new grass.jupyter does not have translated messages now). It would be good to discuss this on grass-dev and arrive at some best practice.

[Viech]

1. You are using % formatting, but in this context .format() or f-string would be more appropriate with current Python. Any reason for that?

Likely because this MR is old and PyGRASS used that style at the time. I don't normally use %.

2. Your error messages are not translatable (not marked with _(...), .format() or % are then needed, not f-string). Is that intentional? Python does not translate its error messages, but in GRASS we generally do, although for programming-only messages it is permissible not to translate (most of the new grass.jupyter does not have translated messages now). It would be good to discuss this on grass-dev and arrive at some best practice.

Same idea. Unless I missed something, I would've copied the style I found. Exception translation is something I don't think I've ever seen in any project, though. Users who can understand Python exceptions are very likely to understand English while users who see exceptions as gibberish will just post them in an issue and you'd end up with non-English exceptions on the tracker.