Infra: generate an iCalendar file of the release dates#4704
Closed
hugovk wants to merge 2 commits intopython:mainfrom
Closed
Infra: generate an iCalendar file of the release dates#4704hugovk wants to merge 2 commits intopython:mainfrom
hugovk wants to merge 2 commits intopython:mainfrom
Conversation
Contributor
|
It would be useful indeed. Thanks. |
encukou
reviewed
Nov 13, 2025
| pytest-cov | ||
|
|
||
| # For python-releases.ical | ||
| icalendar |
Member
There was a problem hiding this comment.
Obligatory “supply chain” security question: do we trust icalendar maintainers and their operational security?
This could be tasty vector for running code on core dev boxes.
cc @sethmlarson
Maybe consider generating “manually”? iCal is a simple, stable text-based format.
Contributor
There was a problem hiding this comment.
@encukou I would recommend generating the ICS file manually within the code instead of relying on a library. The format is quite simple, especially for the use-case we need :)
Member
There was a problem hiding this comment.
I've proposed a simpler alternative at #4705 following this suggestion.
A
Member
Author
|
Closed in favour of #4705. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Now we have all the Python release dates in a single file (https://github.com/python/peps/blob/main/release_management/python-releases.toml) and generate some JSON files from it (#4702, #4331), it's easy to generate other useful files as well.
One useful file is an iCalendar
.icsfile that can be imported to calendars.The Fedora Python team are generating one at https://github.com/fedora-python/python-release-schedule-ical through scraping the PEP HTML files. I'm using this and have found it extremely useful. If we generate one here, they could retire that repo if they like.
Differences between the two:
[email protected]. I used a similar pattern, but added a hyphen to avoid conflicts:[email protected]cc @hroncok @hrnciar from Fedora Python, would this be useful for you?
📚 Documentation preview 📚: https://pep-previews--4704.org.readthedocs.build/