alt Hacker NewsThis will be huge at the place I work!
I’m unfamiliar with the PEP process. How long until this makes it into a Python version?
Replies
joerick • yesterday at 6:54 PM
It should land in 3.15, so October next year. https://peps.python.org/pep-0790/
This will be huge at the place I work!
I’m unfamiliar with the PEP process. How long until this makes it into a Python version?
It should land in 3.15, so October next year. https://peps.python.org/pep-0790/
This one is scheduled to land in the next "minor" version, 3.15. Python has an annual release cadence; 3.14 came out recently and 3.15 is due next October.
In general, most PEPs are authored targeting the "next minor version" at the time of proposal; but they may be intentionally deferred at the start, and sometimes the process can take multiple years anyway.
There are also PEPs that don't involve any change to the Python language, standard library or interpreter. In particular, there are PEPs that exist simply to document existing practice (or changes thereto), PEPs that concern governance (the Python Software Foundation, the Steering Council etc.), and PEPs that cover related special interests, such as packaging standards (which in turn can range from technical details about how metadata is formatted, to changes in PyPI's API).
https://peps.python.org/pep-0000/