GeezerVison is showing github.com — Add version requirements to the translation section of the dev guide · Issue #1586 · python/devguide
Add version requirements to the translation section of the dev guide #1586Description
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 python/docsbuild-scripts#248 (comment)
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. ActivityStanFromIreland commented on Jun 20, 2025 I recommend the latest non-alpha branch, which is what most translations focus on. (e.g. all TX teams) AA-Turner commented on Jun 20, 2025 Per the same thread, I'd support stating that we target the current latest (released) minor version.
A willingc commented on Jun 20, 2025 CollaboratorAuthor More actions lysnikolaou commented on Jun 23, 2025 I agree we should propose targeting the current latest minor version. However, I don't think that should be a hard requirement. Many language teams start as one person doing most of the work and that might mean they might not be able to translate all of the required files in time, at which point instead of doing more translations they would need to spend time on updating to the most recent version.
Thus I feel that becoming part of the language picker should be okay with even a slightly older version. Having something documented in their native language is better for our users than having nothing. Reacted by Hugo van Kemenade StanFromIreland commented on Aug 18, 2025 (This was removed from the PR, as no conclusion was reached and still needs further discussion) StanFromIreland commented on Aug 29, 2025 Reacted by Octavian Mustafa AA-Turner commented on Aug 29, 2025 The current last minor version is X.Y, rather than X.Y.Z. As I said in that issue, given the website shows the latest changes, not frozen at the patch release, I think the translation target should be the state of the latest minor branch (i.e., currently 3.13).
As has been said a few times, the minimums in PEP 545 are very little -- a reader with no proficiency in English will get almost nothing out of it. We shouldn't aim to lower those requiremens, and perhaps should consider revisiting them to e.g. require that more of the stdlib or reference is translated before publication into the much more visible language switcher.
A Reacted by Octavian Mustafa StanFromIreland commented on Aug 29, 2025
We shouldn't aim to lower those requiremens, and perhaps should consider revisiting them to e.g. require that more of the stdlib or reference is translated before publication into the much more visible language switcher.
I previously suggested modifications, based on the statistically most read pages, in https://discuss.python.org/t/pep-545-update-language-switcher-requirements/75750.
I however tried to keep the amount of translation similar, adding to the switcher has been a motivational milestone for translations, raising the requirements may lead to de-motivation and unfortunately translators burning out. Reacted by Octavian Mustafa ASHWINS378 commented on Oct 23, 2026 willingc commented on Oct 23, 2026 CollaboratorAuthor More actions StanFromIreland commented on Oct 23, 2026 I think we still need to agree on the exact requirement. We could accept either the latest alpha if we're close to the first release, or whatever is currently live at /3/ if we're not.
MetadataMetadataStatusShow more project fields
DevelopmentNo branches or pull requestsIssue actions
|