
web.archive.org/web/20221019223854/https:/discuss.python.org/t/pep-602-annual-release-cycle-for-python/2296/79
Preview meta tags from the web.archive.org website.
Thumbnail

Search Engine Appearance
https://web.archive.org/web/20221019223854/https:/discuss.python.org/t/pep-602-annual-release-cycle-for-python/2296/79
[ACCEPTED] PEP 602: Annual Release Cycle for Python
I’ve been asked by the Steering Council to move parts of PEP 596 that discuss the release cycle changes to its separate PEP. Here it is. I’ve also incorporated feedback from previous discussion. Abstract This document…
Bing
[ACCEPTED] PEP 602: Annual Release Cycle for Python
https://web.archive.org/web/20221019223854/https:/discuss.python.org/t/pep-602-annual-release-cycle-for-python/2296/79
I’ve been asked by the Steering Council to move parts of PEP 596 that discuss the release cycle changes to its separate PEP. Here it is. I’ve also incorporated feedback from previous discussion. Abstract This document…
DuckDuckGo

[ACCEPTED] PEP 602: Annual Release Cycle for Python
I’ve been asked by the Steering Council to move parts of PEP 596 that discuss the release cycle changes to its separate PEP. Here it is. I’ve also incorporated feedback from previous discussion. Abstract This document…
General Meta Tags
14- title[ACCEPTED] PEP 602: Annual Release Cycle for Python - #79 by hroncok - PEPs - Discussions on Python.org
- charsetutf-8
- descriptionI’ve been asked by the Steering Council to move parts of PEP 596 that discuss the release cycle changes to its separate PEP. Here it is. I’ve also incorporated feedback from previous discussion. Abstract This document…
- discourse_theme_id2
- discourse_current_homepagecategories
Open Graph Meta Tags
9- og:site_nameDiscussions on Python.org
- og:typewebsite
- og:imagehttps://web.archive.org/web/20250704145726im_/https://us1.discourse-cdn.com/flex002/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png
- og:urlhttps://web.archive.org/web/20250704145726/https://discuss.python.org/t/accepted-pep-602-annual-release-cycle-for-python/2296/79
- og:title[ACCEPTED] PEP 602: Annual Release Cycle for Python
Twitter Meta Tags
5- twitter:cardsummary
- twitter:imagehttps://web.archive.org/web/20250704145726im_/https://us1.discourse-cdn.com/flex002/uploads/python1/original/1X/f93ff97c4f381b5e8add5a0c163b4ded29f20ed7.png
- twitter:urlhttps://web.archive.org/web/20250704145726im_/https://discuss.python.org/t/accepted-pep-602-annual-release-cycle-for-python/2296/79
- twitter:title[ACCEPTED] PEP 602: Annual Release Cycle for Python
- twitter:descriptionLooking at current proposal in PEP 596 and the expected Fedora 33 schedule. At 2020-08-25, Fedora 33 Beta Freeze starts. At that date, Python 3.9.0 is still at b4. Having it as rc1 would be much better. When Python slips, we would satisfy with b4. We want to avoid b3, because there are dangerous changes happening between betas, such as changing the bytecode magic number (and we need to rebuild the whole distro when this happens which is hard after beta freeze, but not impossible). At 2020-10-...
Link Tags
40- alternate nofollowhttps://discuss.python.org/t/accepted-pep-602-annual-release-cycle-for-python/2296.rss
- apple-touch-iconhttps://web.archive.org/web/20250704145726im_/https://us1.discourse-cdn.com/flex002/uploads/python1/optimized/1X/4c06143de7870c35963b818b15b395092a434991_2_180x180.png
- canonicalhttps://web.archive.org/web/20250704145726/https://discuss.python.org/t/accepted-pep-602-annual-release-cycle-for-python/2296?page=4
- iconhttps://web.archive.org/web/20250704145726im_/https://us1.discourse-cdn.com/flex002/uploads/python1/optimized/1X/9997f0605d56c4bfecd63594f52f42cdafd6b06a_2_32x32.png
- manifest/web/20250704145726/https://discuss.python.org/manifest.webmanifest