Add version requirements to the translation section of the dev guide
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 1k
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 12
Description
but the minimum requirements are now fulfilled for all of 3.12, 3.13 and 3.14.
Hmm, we don't actually state in PEP 545 which version should meet the requirements. Something we should probably add in future amendments. cc @JulienPalard / @willingc
Originally posted by @StanFromIreland in https://github.com/python/docsbuild-scripts/issues/248#issuecomment-2987912733
This is a good suggestion. I'm opening an issue on the devguide to begin discussion about what makes sense among contributors to be a sensible default.
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
Start with the translation section of the dev guide and review the linked PEP 545 discussion, including the stated Python versions 3.12, 3.13, and 3.14. Done means contributors have agreed on and documented the version requirements for that section.
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