🔍 Translation review needed after CPython sync (2026-10-01)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- documentation, localization
Research direction
Open library/asyncio-eventloop.po, library/asyncio-stream.po, and library/ssl.po and inspect the six untranslated entries introduced by the CPython 3.14 sync. Compare them with the corresponding source strings and surrounding Farsi translations, then review the PO changes; done means all six entries have accurate Farsi translations.
Written by the indexing model from the issue text.
Description
Summary
- ✏️ 6 new untranslated strings in 3 files
✏️ New untranslated strings
Brand-new source strings with no close match to an existing translation.
library/asyncio-eventloop.po (1 new untranslated)
Raises a ``ValueError`` if ``ssl.check_hostname`` is ``True`` and ``server_hostname`` is not supplied.
library/asyncio-stream.po (1 new untranslated)
Raises a ``ValueError`` if ``sslcontext.check_hostname`` is ``True`` and ``server_hostname`` is not supplied.
library/ssl.po (4 new untranslated)
If the callback assigns a new context to :attr:`SSLSocket.context`, any further ClientHello message on the same connection (for example after a TLS 1.3 HelloRe…
After the callback assigns a new :attr:`SSLSocket.context`, later ClientHello messages on the connection are dispatched to the new context's *sni_callback*.
The *server_side*, *server_hostname* and *session* parameters have the same meaning as in :meth:`SSLContext.wrap_socket`, and are validated in the same way: in…
The *server_side*, *server_hostname* and *session* parameters are now validated as :meth:`SSLContext.wrap_socket` validates them. Previously a context with :at…
Triggered by sync with 3.14 (commit 7f62e073).
- Dominant language
- Python
- Stars
- 55
- Forks
- 14
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from python/python-docs-fa
-
تغییرات خودکار در ترجمهها
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
python/python-docs-fa#86 ·
-
تغییرات خودکار در ترجمهها
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
python/python-docs-fa#85 ·
-
ایشوی جامع
Difficulty 5/5 Over a week Newbie friendliness 20/100
python/python-docs-fa#83 ·
All issues in python/python-docs-fa
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
debpalash/VoiceStudio#2624 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Make Catch2 optional when `RDK_BUILD_CPP_TESTS=OFF`Possibly taken @pechersky claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
There are a few redundant calls to `fdesc._setCloseOnExec()`Possibly taken @gudnimg claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day