-
Notifications
You must be signed in to change notification settings - Fork 619
don't denote old versions as 'the newest major release of Python' #2284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
I was unable to find out where the "is the newest major release of the Python programming language" string for 3.11.x was located (but I did not devote much time for the investigation either ...): https://www.python.org/downloads/release/python-3114/ For 3.11.4, it is true that it's the newest major release of Python, but that's not true for 3.11.3 and older. Perhaps "the newest stable release of Python" is more accurate. |
This reverts commit 252ddbd.
(I reverted 252ddbd as it broke CI, and I have no time to investigate that) |
It seems like these are only present in the |
Yep, makes sense. |
The changes here are for the fixtures. The contents itself is managed in the CMS in the live database. Happy to merge, but it will have no impact on the live pages at python.org. Someone from @python/python-release-managers will need to update the existing CMS contents. |
If it has no impact, there's no need to merge :) Thanks for the info! |
The change to |
See also python/cpython#105844