Add beta release dates to JSON #1554
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
See also python/peps#4331, which would also provide these data. A |
You can split this to another PR. Thanks! |
Splitted to #1555 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ref. #999 (and #998).
Fix Python 3.14 first release dateNot adding the beta release dates in Status of Python versions page, though this data would be useful in translations automations. The translation teams start to translate a version after the beta release. It would be used in transifex-automations (which now scrapes Python.org downloads page to get the data) and dashboard projects.
📚 Documentation preview 📚: https://cpython-devguide--1554.org.readthedocs.build/