Based on this statement in PEP 1, I would have expected these PEPs to have status 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”.
It might very well be the case that I misunderstand when a PEP is supposed to be marked Final. If that is the case, perhaps someone here could clarify to me when the transition happens.
Heh. If only my clients would upgrade to 3.9, I might be more familiar with it. I agree it looks like this and PEP 572 – Assignment Expressions should be Final. I’m not sure about the typing ones, I’m not a big user.
Of course, some of these PEPs have parts that haven’t yet been completed (e.g. final removal of the packages listed in PEP 594 in Python 3.13, or concerns about PEP 646), and many of the typing PEPs might want to wait until implementation in the major type checkers to be considered final (which @Jelle would be the person to ask about that), like the packaging PEPs do. The rest are likely suitable for being marked Final, pending confirmation by the author/sponsor and no other outstanding considerations.
You can also list all accepted PEPs, e.g. by version, category, etc., as there are likely others that haven’t yet been marked final that should be.
In any case, I’ve opened an issue to document, discuss and track the PEPs that probably should be updated, if you’d like to help: