Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🔍 Translation review needed after CPython sync (2026-10-05)

Open Beginner friendly
#86 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
67/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
localization

Research direction

Read the changed source strings from the CPython 3.14 sync, then review library/ctypes.po and c-api/exceptions.po. Update the fuzzy Persian translation and translate the two new strings; the work is done when the translations are complete and the fuzzy entry is resolved.

Written by the indexing model from the issue text.

Description

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

Summary

  • 🔍 1 newly fuzzy strings in 1 files
  • ✏️ 2 new untranslated strings in 1 files

🔍 Newly fuzzy strings

The source text changed slightly, so the existing translation (msgstr) may need updating. - is the old source, + the new.

library/ctypes.po (1 new fuzzy)
- Note that if the Python interpreter is statically linked, this will be ``None``, as ``dlopen`` is not possible in this case.
+ If the Python interpreter is statically linked, this may be ``None``.
  msgstr: توجه داشته باشید که اگر مفسر پایتون به‌صورت ایستا پیوند شده باشد، این مقدار ``None`` خواهد بود، زیرا در این حالت ``dlopen`` ممکن نیست.

✏️ New untranslated strings

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

c-api/exceptions.po (2 new untranslated)
The check is based on the remaining C stack space of the current thread, not on a count of calls, so it is unaffected by :c:func:`Py_SetRecursionLimit` and :fu…
The check is based on the remaining C stack space.  Previously, a separate counter of C-level calls was used.

Triggered by sync with 3.14 (commit 01b5df62).

Dominant language
Python
Stars
55
Forks
14
Avg merge
1d 21h
Merged PRs (30d)
8

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.