Add version requirements to the translation section of the dev guide

Open
#1,586 8 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

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.

Description

topic-documentation

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.

Dominant language
Python
Stars
2.1k
Forks
1k
Avg merge
2d 12h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

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.

More from python/devguide

All issues in python/devguide

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.