Point users to peps.python.org/release-schedule.ics

Open
#72 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
release

Research direction

Review the README and the current output represented by the official release-schedule.ics. Identify where event names are produced, then verify that deprecation notices appear in event names while the existing checklist behavior remains intact. The issue provides no test file or code entry point, and the repository is marked deprecated.

Written by the indexing model from the issue text.

Description

Thanks to https://github.com/python/peps/pull/4705 there is now https://peps.python.org/release-schedule.ics

We should point our users to it. GitHub pages does not support HTTP redirects, so we can:

  • document the new location in readme
  • copy the official ics instead of scraping HTML
  • include deprecation notices in even descriptions
  • later: include deprecation notices in event names
Dominant language
Python
Stars
5
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.