PEP 765: Disallow return/break/continue that exit a finally block

[mikeshardmind (Michael H)]

@pf_moore

And what’s worse, the only way of fixing it is for the library developer to change the code (and release a new version). Because as far as I can see, the runtime warning filter doesn’t work for syntax warnings:

@pf_moore

While I appreciate that this problem may be very rare, a syntax warning seems like it will cause at least as many problems as we’ve had with other forms of deprecation warnings. IMO, if we think this needs to be prohibited, we should stand by our decision, and simply make it an error. If there’s too much risk of disruption from doing that, I think there’s also too much risk of disruption using a syntax warning.

This has caused CI failures for someone testing 3.14rc1

I’m not sure what I should recommend to this user other than “now you need to suppress specific warnings in your CI at a level above python”; It also feels wrong to change code that is working as intended because of what amounts to a linter warning with no specific plan to actually make it an error.