Python has a notch: New versions of the programming language will now appear each year, instead of every 18 months. This will affect the upcoming Major Version of Python 3.9, which will be brought forward by six months.
According to previous discussions within the Community, Brett Cannon, Python LMA and a member of the Python Steering Council has announced the adoption of PEP 602. This means an annual, and thus shorter Release cycle for Major versions of the language. The announcement was done via the Python mailing list in the name of the Python Steering Council.
PEP 602 is, however, accepted on the condition that further adjustments are made by Python Core Developer Łukasz Langa, had submitted the Proposal in June of this year. The proposed Changes relate to an extension of the beta phases from two to three months, as well as the doubling of the Release-Candidate Phase for two months.
If the new Release cycle is implemented, it will also affect the upcoming Version of Python 3.9. It is then, according to the PEP, 602, 5. October 2020 planned, i.e. about a year after the Release of Python 3.8. Originally Python 3.9 was recognized in Accordance with the current 18-month Release cycle for April, 2021.
Steering Council expected positive effects
The Steering Council according to the updated Release cycle, both the Community and the Core developers offer some advantages.
The increased reliability, to help users to RCs to prepare and to know when the Beta Test can be started. Another expected advantage is the improved coordination of related Releases, with the final Version of Python is. Core Developer will get a better plan, and new Features will be available both to you and to the Community more quickly.
Together with the annual Release schedule, further innovations were incorporated. This is to accommodate users who can't upgrade your Python Version every year. Deprecations will now last two Releases, two years, in contrast to the previous 18 months. It was also working on the stable ABI for extension modules better suited. To improve the support for new Python versions.
But that was not enough: the discussion of PEP 387 is resumed, and a clearer Directive for backward to develop compatibility.
for More information for the adoption of PEP 602 there is the Python mailing list.the