This project is used as a preview, not yet used for production workflow. Integrations efforts are ongoing as well as figuring out the funding.

Please refer to https://devguide.python.org/documentation/translating/ for guidance about the translations.

This project is in a trial period, be cautious while contributing. Setup can still change before being approved as a libre project.

Source strings

206 Strings 100%
Browse Translate
4,804 Words 100%
33,789 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
206 4,804 33,789
All strings Browse Translate Zen
206 4,804 33,789
Read-only strings Browse Translate Zen
8 338 2,330
Strings with any failing checks Browse Translate Zen
7 301 2,007
Failing check: Ellipsis Browse Translate Zen
1 37 323
Failing check: Long untranslated Browse Translate Zen

Overview

Project website docs.python.org
Instructions for translators

See devguide.python.org/documentation/translating.
Project maintainers User avatar rafaelff User avatar josix User avatar m-aciek
Translation license Creative Commons Zero v1.0 Universal
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@github.com:m-aciek/python-docs-weblate.git
Repository branch main
Last remote commit [3.12] gh-126259: Fix "unclosed database" warning in sqlite3 doctest (GH-126260) (#126266) dc52670
github-actions[bot] authored 43 minutes ago
Last commit in Weblate [3.12] gh-126259: Fix "unclosed database" warning in sqlite3 doctest (GH-126260) (#126266) dc52670
github-actions[bot] authored 43 minutes ago
Weblate repository https://hosted.weblate.org/git/python-docs/latest/bugs/
File mask */latest/whatsnew/3.0.po
Translation file Not available
Last change Nov. 8, 2023, 4:40 p.m.
Last change made by None
Language English
Language code en
Text direction Left to right
Number of speakers 1,636,485,517
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 206 4,804 33,789
Translated 100% 206 100% 4,804 100% 33,789
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 206 100% 4,804 100% 33,789
Failing checks 3% 8 7% 338 6% 2,330
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 206 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

4,804
Hosted words
206
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Source string added
Removed :func:`reload`. Use :func:`!imp.reload`.
11 months ago
User avatar None

Source string added
For porting C extensions to Python 3.0, please see :ref:`cporting-howto`.
11 months ago
User avatar None

Source string added
It is not recommended to try to write source code that runs unchanged under both Python 2.6 and 3.0; you'd have to use a very contorted coding style, e.g. avoiding ``print`` statements, metaclasses, and much more. If you are maintaining a library that needs to support both Python 2.6 and Python 3.0, the best approach is to modify step 3 above by editing the 2.6 version of the source code and running the ``2to3`` translator again, rather than editing the 3.0 version of the source code.
11 months ago
User avatar None

Source string added
Run the ``2to3`` source-to-source translator over your source code tree. (See :ref:`2to3-reference` for more on this tool.) Run the result of the translation under Python 3.0. Manually fix up any remaining issues, fixing problems until all tests pass again.
11 months ago
User avatar None

Source string added
(Still using 2.6:) Turn on the :option:`!-3` command line switch. This enables warnings about features that will be removed (or change) in 3.0. Run your test suite again, and fix code that you get warnings about until there are no warnings left, and all your tests still pass.
11 months ago
User avatar None

Source string added
Port to Python 2.6. This should be no more work than the average port from Python 2.x to Python 2.(x+1). Make sure all your tests pass.
11 months ago
User avatar None

Source string added
(Prerequisite:) Start with excellent test coverage.
11 months ago
User avatar None

Source string added
For porting existing Python 2.5 or 2.6 source code to Python 3.0, the best strategy is the following:
11 months ago
User avatar None

Source string added
Porting To Python 3.0
11 months ago
User avatar None

Source string added
The net result of the 3.0 generalizations is that Python 3.0 runs the pystone benchmark around 10% slower than Python 2.5. Most likely the biggest cause is the removal of special-casing for small integers. There's room for improvement, but it will happen after 3.0 is released!
11 months ago
Browse all translation changes