Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork932
Replace local release-cycle.json with PEPs repo version#1685
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
include/release-cycle.json Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This will break scripts that depend on this file, e.g. your GitHub tools.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Yeah, they also need updating to point tohttps://peps.python.org/api/release-cycle.json
Let's update/notify the ones we know about before merging.
This file is now generated and published from the PEPs repo (python/peps#4331) and will be removed from the devguide soon (python/devguide#1685).
AA-Turner commentedNov 10, 2025
It might be better ad interim to have the devguide just copy & republish (or redirect to?) the PEPs A |
hugovk commentedNov 10, 2025
Yes, that's a good idea. |
This file is now generated and published from the PEPs repo (python/peps#4331) and will be removed from the devguide soon (python/devguide#1685).
hugovk commentedNov 10, 2025
I've opened a bunch of PRs to update most of the public GitHub repos using this file.
Hm, seeing as this was never published underhttps://devguide.python.org/ and people were just fetching the file directly from the repo using something like It's just a file in the repo. So we'd need to add some automation that downloads the new file, and thencommits it here. Or we do update it manually from time to time. I'm not so keen on either of those. Because we never "officially published" this file, it was something used internally in this repo, I suggest we wait a little while for the important PRs above to be merged, then go ahead with this one. And rather than completely delete the file here (which would give 404) we could put an error message in the file saying to use the new file instead. This could either be plain text, or some basic JSON such as |
AA-Turner commentedNov 10, 2025
Ah, yes. Perhaps let's wait at least a fortnight, but no later than the end of the year -- the only downside will be stale data in the devguide (I don't propose we'd make any further updates here). I'd prefer to delete entirely, but adding some sort of note in the file could make sense. We could also add something to README / use an announcement issue. A 404 isn't terrible as it is an early and hard failure, whereas changing the JSON structure could have confusing errors. Luckily though the impact doesn't seem massive, there's only a dozen or so third-party uses on GitHub. A |
Uh oh!
There was an error while loading.Please reload this page.
We now generate and publish
release-cycle.jsonfrom the PEPs repo (python/peps#4331) so can use that directly and don't need to duplicate this data.📚 Documentation preview 📚:https://cpython-devguide--1685.org.readthedocs.build/