🚀

Final task, mark the the PEP as Final:

Once a PEP has been accepted, the reference implementation must be completed. When the reference implementation is complete and incorporated into the main source code repository, the status will be changed to “Final”.

https://peps.python.org/pep-0001/#pep-review-resolution

There are a bunch of warnings when executing the test suite now:

• in Lib/test/test_grammar.py (e.g., test_break_in_finally)
• in Lib/test/test_functools.py (e.g., test_double_wrapped_methods)
• in Lib/multiprocessing/connection.py (but this one has already been reported in return-in-finally in multiprocessing/connection.py #131233)

I'm re-opening the issue so that we fix the issues in the tests but you can open a separate issue if you want.

#130087 seems to have introduce a regression were AST folding is now applied even if it shouldn't be. E.g.

# test.py
match a:
  case -1+2j:
    pass

With Python 3.13 (or 3.14a6)

$ python3.13 -m ast test.py
        ...
            match_case(
               pattern=MatchValue(
                  value=BinOp(
                     left=UnaryOp(
                        op=USub(),
                        operand=Constant(value=1)),
                     op=Add(),
                     right=Constant(value=2j))),
               body=[...

After #130087

$ python -m ast test.py
        ...
            match_case(
               pattern=MatchValue(
                  value=Constant(value=(-1+2j))),
               body=[...

#130087 seems to have introduce a regression were AST folding is now applied even if it shouldn't be. E.g.

Thanks, this is now fixed.

@iritkatriel I believe this memset is unnecessary:

Here is PR: #131745

We do this in other places - set everything to 0 and then override other fields. If someone adds a new field which should be initialised to 0 they will probably not bother to update initialisation.

I see. Closing it then.