🔍 Translation review needed after CPython sync (2026-11-14)

Open Beginner friendly
  • Is something wrong?
#137 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
62/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
documentation, internationalization, localization

Research direction

The four untranslated entries are in whatsnew/changelog.po, each with a msgid that is a changelog line for a CPython fix (zipfile UTF-8 flag, random CLI, hashlib PBKDF2 under FIPS, MD5 test skips). Start by reading the nearby translated entries in that file to match Sphinx markup such as :mod:, :ref: and double backticks, and to match the glossary terms already used. Done when each new msgstr is filled in Persian with the markup intact and the file still parses as valid .po.

Written by the indexing model from the issue text.

Description

3.15 تغییرات خودکار در ترجمه‌ها

Summary

  • ✏️ 4 new untranslated strings in 1 files

✏️ New untranslated strings

Brand-new source strings with no close match to an existing translation.

whatsnew/changelog.po (4 new untranslated)
:gh:`152845`: Fix :mod:`zipfile` dropping the UTF-8 (EFS) flag for existing entries when rewriting an archive in append mode, and honor an explicitly set flag …
:gh:`161452`: Fix the :mod:`random` :ref:`command-line interface <random-cli>` printing a random float for a zero or negative integer input instead of failing …
:gh:`161739`: ``test_hashlibtest_pbkdf2_hmac_c`` from ``test_haslib`` no longer fails with ``ValueError: [Provider routines] invalid salt length`` with FIPS en…
:gh:`161263`: Skip tests which use MD5 algorithm for WWW-Authenticate challenges when libssl is in FIPS mode.

Triggered by sync with 3.15 (commit 01d4c7ad).

Dominant language
Python
Stars
105
Forks
20
Avg merge
20h 44m
Merged PRs (30d)
1

Getting set up

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/python-docs-fa

All issues in python/python-docs-fa

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.