Better exception localization

[blhsing (Ben Hsing)]

@Rosuav

Perhaps more importantly though, having a syntax that comes immediately after an otherwise-complete statement is going to cause a lot of confusion.

And will simply not work in REPL, in which each complete statement is executed immediately.

@Rosuav

PEP 463 proposed similar functionality, but for a number of reasons, it didn’t get traction. One of those reasons was the difficulty of finding a really good syntax, but it wasn’t the only one, and I suspect that, even if someone does come up with the most gorgeous way to write this, it’s still not going to be accepted.

Thanks for the link to PEP-463, which I wasn’t aware of before. I think one problem with any attempt to generalize exception handling as an expression is that most exception names are pretty long to begin with, so including it and the default value on the same line as the expression that may produce the error is likely to make the line too long to fit the maximum line width of many style recommendations.

I think most use cases listed in PEP-463 can be more succinctly expressed with the operators proposed in PEP-505, which Guido, who rejected PEP-463, is an avid proponent of, and which I suggest the OP to take a look at as well.