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

14 Strings 100%
Browse Translate
400 Words 100%
2,559 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
14 400 2,559
All strings Browse Translate Zen
14 400 2,559
Read-only strings Browse Translate Zen
1 23 131
Strings with any failing checks Browse Translate Zen
1 23 131
Failing check: Ellipsis 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-90562: Mention slots pitfall in dataclass docs (GH-107391) (#119351) b570780
github-actions[bot] authored 10 hours ago
Weblate repository https://hosted.weblate.org/git/python-docs/latest/bugs/
File mask */latest/library/codeop.po
Translation file Not available
Last change None
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 14 400 2,559
Translated 100% 14 100% 400 100% 2,559
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 14 100% 400 100% 2,559
Failing checks 7% 1 5% 23 5% 131
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 14 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

400
Hosted words
14
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

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
Instances of this class have :meth:`__call__` methods identical in signature to :func:`compile_command`; the difference is that if the instance compiles program text containing a :mod:`__future__` statement, the instance 'remembers' and compiles all subsequent program texts with the statement in force.
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
Instances of this class have :meth:`__call__` methods identical in signature to the built-in function :func:`compile`, but with the difference that if the instance compiles program text containing a :mod:`__future__` statement, the instance 'remembers' and compiles all subsequent program texts with the statement in force.
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
It is possible (but not likely) that the parser stops parsing with a successful outcome before reaching the end of the source; in this case, trailing symbols may be ignored instead of causing an error. For example, a backslash followed by two newlines may be followed by arbitrary garbage. This will be fixed once the API for the parser is better.
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
The *symbol* argument determines whether *source* is compiled as a statement (``'single'``, the default), as a sequence of :term:`statement` (``'exec'``) or as an :term:`expression` (``'eval'``). Any other value will cause :exc:`ValueError` to be raised.
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
If there is a problem with *source*, an exception will be raised. :exc:`SyntaxError` is raised if there is invalid Python syntax, and :exc:`OverflowError` or :exc:`ValueError` if there is an invalid literal.
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
Tries to compile *source*, which should be a string of Python code and return a code object if *source* is valid Python code. In that case, the filename attribute of the code object will be *filename*, which defaults to ``'<input>'``. Returns ``None`` if *source* is *not* valid Python code, but is a prefix of valid Python code.
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
To do just the former:
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
The :mod:`codeop` module provides a way of doing each of these things, and a way of doing them both.
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
Remembering which future statements the user has entered, so subsequent input can be compiled with these in effect.
6 months ago
User avatar None

Source string added

  1. Python documentation
  2. 3.12
  3. latest/library/codeop
  4. English
Being able to tell if a line of input completes a Python statement: in short, telling whether to print '``>>>``' or '``...``' next.
6 months ago
Browse all translation changes