GitHub Actions: Test on Python 3.14

[cclauss]

Python 3.14 -- the π version
https://www.python.org/downloads/release/python-3140/
https://docs.python.org/3.14/whatsnew/3.14.html#porting-to-python-3-14

Blocked by:

• https://docs.python.org/3.14/whatsnew/3.14.html#pep-765-disallow-return-break-continue-that-exit-a-finally-block
• https://docs.python.org/3.14/reference/compound_stmts.html#finally-clause

Changed in version 3.14: The compiler emits a SyntaxWarning when a return, break or continue appears in a finally block (see PEP 765).

I am out of my depth on this one... Someone else would need to craft the correct solution.

[jakkdl]

it appears one (or more) of the test files have a return in a finally. Ideally the compile call should have a better error message and tell what file fails, but you can also try running all the files in the tests/eval_files (tests/autofix_files you can then fix with --generate-autofix) to see where the return in a finally is.

[cclauss]

Do we want to modify the test files to be compatible with Python 3.14, or do we want to update the linter to complain about test files that are not compatible with Python 3.14?

[jakkdl]

I think we can probably just modify the tests that do have returns in finally so they work on 3.14. Ideally there'd be support to specify the maximum python version and not just minimum python version in the test infra, but I'm not sure it's worth the effort.
And yeah ideally the compile call would also be improved, but I don't think that's a blocker for this PR.

[A5rocks]

a) probably just pass a filename argument to Plugin.from_source and thread it to ast.parse?
b) I think the issue is tests/eval_files/async910.py, it says the path in the stack frames when pytest prints out the locals.