python / python/typing_extensions
Python version support policy
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 583
- Forks
- 146
- Avg merge
- 10h 11m
- Merged PRs (30d)
- 5
Description
I think it would be useful to have an explicit Python version support policy.
Here's a few aspects I'd like to propose:
- We support all feature versions (3.x) of Python from the the beginning of the release candidate phase until they reach end-of-life.
- We attempt to support pre-releases before the RC phase too, especially while they're in beta, but there may be some mismatches.
- We drop support for old versions sometime after they reach EOL, usually not immediately but only when CI maintenance starts to become a burden.
- We aim to support all bugfix releases (3.x.y) of supported feature versions. However, to keep CI sane we don't necessarily test against all possible bugfix releases.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the repository documentation and CI configuration that describe Python version support, then compare them with the proposed policy. Done means the supported-version policy is documented clearly and agrees with the project’s stated CI coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100