sync mit Transifex

Author: sba72

library/__future__.po

@@ -2,19 +2,19 @@
 # Copyright (C) 2001 Python Software Foundation
 # This file is distributed under the same license as the Python package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+# 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-09-05 16:53+0200\n"
-"PO-Revision-Date: 2025-09-16 00:00+0000\n"
+"POT-Creation-Date: 2026-09-23 19:04+0000\n"
+"PO-Revision-Date: 2026-05-08 17:17+0000\n"
 "Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
-"Language: de\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Language: de\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
 #: ../../library/__future__.rst:2
@@ -27,17 +27,17 @@ msgstr ""
 
 #: ../../library/__future__.rst:11
 msgid ""
-"Imports of the form ``from __future__ import feature`` are called :ref:"
-"`future statements <future>`. These are special-cased by the Python compiler "
-"to allow the use of new Python features in modules containing the future "
-"statement before the release in which the feature becomes standard."
+"Imports of the form ``from __future__ import feature`` are called "
+":ref:`future statements <future>`. These are special-cased by the Python "
+"compiler to allow the use of new Python features in modules containing the "
+"future statement before the release in which the feature becomes standard."
 msgstr ""
 
 #: ../../library/__future__.rst:16
 msgid ""
 "While these future statements are given additional special meaning by the "
-"Python compiler, they are still executed like any other import statement and "
-"the :mod:`!__future__` exists and is handled by the import system the same "
+"Python compiler, they are still executed like any other import statement and"
+" the :mod:`!__future__` exists and is handled by the import system the same "
 "way any other Python module would be. This design serves three purposes:"
 msgstr ""
 
@@ -49,18 +49,18 @@ msgstr ""
 
 #: ../../library/__future__.rst:24
 msgid ""
-"To document when incompatible changes were introduced, and when they will be "
-"--- or were --- made mandatory.  This is a form of executable documentation, "
-"and can be inspected programmatically via importing :mod:`!__future__` and "
-"examining its contents."
+"To document when incompatible changes were introduced, and when they will be"
+" --- or were --- made mandatory.  This is a form of executable "
+"documentation, and can be inspected programmatically via importing "
+":mod:`!__future__` and examining its contents."
 msgstr ""
 
 #: ../../library/__future__.rst:29
 msgid ""
-"To ensure that :ref:`future statements <future>` run under releases prior to "
-"Python 2.1 at least yield runtime exceptions (the import of :mod:`!"
-"__future__` will fail, because there was no module of that name prior to "
-"2.1)."
+"To ensure that :ref:`future statements <future>` run under releases prior to"
+" Python 2.1 at least yield runtime exceptions (the import of "
+":mod:`!__future__` will fail, because there was no module of that name prior"
+" to 2.1)."
 msgstr ""
 
 #: ../../library/__future__.rst:34
@@ -193,17 +193,16 @@ msgstr ""
 
 #: ../../library/__future__.rst:98
 msgid ""
-"where, normally, *OptionalRelease* is less than *MandatoryRelease*, and both "
-"are 5-tuples of the same form as :data:`sys.version_info`::"
+"where, normally, *OptionalRelease* is less than *MandatoryRelease*, and both"
+" are 5-tuples of the same form as :data:`sys.version_info`::"
 msgstr ""
 
 #: ../../library/__future__.rst:101
 msgid ""
 "(PY_MAJOR_VERSION, # the 2 in 2.1.0a3; an int\n"
 " PY_MINOR_VERSION, # the 1; an int\n"
 " PY_MICRO_VERSION, # the 0; an int\n"
-" PY_RELEASE_LEVEL, # \"alpha\", \"beta\", \"candidate\" or \"final\"; "
-"string\n"
+" PY_RELEASE_LEVEL, # \"alpha\", \"beta\", \"candidate\" or \"final\"; string\n"
 " PY_RELEASE_SERIAL # the 3; an int\n"
 ")"
 msgstr ""
@@ -239,16 +238,16 @@ msgstr ""
 msgid ""
 "*CompilerFlag* is the (bitfield) flag that should be passed in the fourth "
 "argument to the built-in function :func:`compile` to enable the feature in "
-"dynamically compiled code.  This flag is stored in the :attr:`_Feature."
-"compiler_flag` attribute on :class:`_Feature` instances."
+"dynamically compiled code.  This flag is stored in the "
+":attr:`_Feature.compiler_flag` attribute on :class:`_Feature` instances."
 msgstr ""
 
 #: ../../library/__future__.rst:133
 msgid ""
 "``from __future__ import annotations`` was previously scheduled to become "
 "mandatory in Python 3.10, but the change was delayed and ultimately "
-"canceled. This feature will eventually be deprecated and removed. See :pep:"
-"`649` and :pep:`749`."
+"canceled. This feature will eventually be deprecated and removed. See "
+":pep:`649` and :pep:`749`."
 msgstr ""
 
 #: ../../library/__future__.rst:141

library/__main__.po

@@ -2,19 +2,19 @@
 # Copyright (C) 2001 Python Software Foundation
 # This file is distributed under the same license as the Python package.
 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
-#
+# 
 #, fuzzy
 msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2026-09-05 16:53+0200\n"
-"PO-Revision-Date: 2025-09-16 00:00+0000\n"
+"POT-Creation-Date: 2026-09-23 19:04+0000\n"
+"PO-Revision-Date: 2026-05-08 17:17+0000\n"
 "Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
-"Language: de\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
+"Language: de\n"
 "Plural-Forms: nplurals=2; plural=(n != 1);\n"
 
 #: ../../library/__main__.rst:2
@@ -41,8 +41,8 @@ msgstr ""
 msgid ""
 "Both of these mechanisms are related to Python modules; how users interact "
 "with them and how they interact with each other.  They are explained in "
-"detail below.  If you're new to Python modules, see the tutorial section :"
-"ref:`tut-modules` for an introduction."
+"detail below.  If you're new to Python modules, see the tutorial section "
+":ref:`tut-modules` for an introduction."
 msgstr ""
 
 #: ../../library/__main__.rst:25
@@ -121,8 +121,8 @@ msgstr ""
 
 #: ../../library/__main__.rst:67
 msgid ""
-"the Python module or package passed to the Python interpreter with the :"
-"option:`-m` argument:"
+"the Python module or package passed to the Python interpreter with the "
+":option:`-m` argument:"
 msgstr ""
 
 #: ../../library/__main__.rst:70
@@ -193,17 +193,17 @@ msgstr ""
 
 #: ../../library/__main__.rst:118
 msgid ""
-"Some modules contain code that is intended for script use only, like parsing "
-"command-line arguments or fetching data from standard input.  If a module "
-"like this was imported from a different module, for example to unit test it, "
-"the script code would unintentionally execute as well."
+"Some modules contain code that is intended for script use only, like parsing"
+" command-line arguments or fetching data from standard input.  If a module "
+"like this was imported from a different module, for example to unit test it,"
+" the script code would unintentionally execute as well."
 msgstr ""
 
 #: ../../library/__main__.rst:123
 msgid ""
 "This is where using the ``if __name__ == '__main__'`` code block comes in "
-"handy. Code within this block won't run unless the module is executed in the "
-"top-level environment."
+"handy. Code within this block won't run unless the module is executed in the"
+" top-level environment."
 msgstr ""
 
 #: ../../library/__main__.rst:127
@@ -238,12 +238,12 @@ msgstr ""
 
 #: ../../library/__main__.rst:151
 msgid ""
-"Note that if the module didn't encapsulate code inside the ``main`` function "
-"but instead put it directly within the ``if __name__ == '__main__'`` block, "
-"the ``phrase`` variable would be global to the entire module.  This is error-"
-"prone as other functions within the module could be unintentionally using "
-"the global variable instead of a local name.  A ``main`` function solves "
-"this problem."
+"Note that if the module didn't encapsulate code inside the ``main`` function"
+" but instead put it directly within the ``if __name__ == '__main__'`` block,"
+" the ``phrase`` variable would be global to the entire module.  This is "
+"error-prone as other functions within the module could be unintentionally "
+"using the global variable instead of a local name.  A ``main`` function "
+"solves this problem."
 msgstr ""
 
 #: ../../library/__main__.rst:158
@@ -260,10 +260,11 @@ msgstr ""
 
 #: ../../library/__main__.rst:167
 msgid ""
-"``main`` functions are often used to create command-line tools by specifying "
-"them as entry points for console scripts.  When this is done, `pip <https://"
-"pip.pypa.io/>`_ inserts the function call into a template script, where the "
-"return value of ``main`` is passed into :func:`sys.exit`. For example::"
+"``main`` functions are often used to create command-line tools by specifying"
+" them as entry points for console scripts.  When this is done, `pip "
+"<https://pip.pypa.io/>`_ inserts the function call into a template script, "
+"where the return value of ``main`` is passed into :func:`sys.exit`. For "
+"example::"
 msgstr ""
 
 #: ../../library/__main__.rst:173
@@ -273,16 +274,16 @@ msgstr ""
 #: ../../library/__main__.rst:175
 msgid ""
 "Since the call to ``main`` is wrapped in :func:`sys.exit`, the expectation "
-"is that your function will return some value acceptable as an input to :func:"
-"`sys.exit`; typically, an integer or ``None`` (which is implicitly returned "
-"if your function does not have a return statement)."
+"is that your function will return some value acceptable as an input to "
+":func:`sys.exit`; typically, an integer or ``None`` (which is implicitly "
+"returned if your function does not have a return statement)."
 msgstr ""
 
 #: ../../library/__main__.rst:180
 msgid ""
-"By proactively following this convention ourselves, our module will have the "
-"same behavior when run directly (i.e. ``python echo.py``) as it will have if "
-"we later package it as a console script entry-point in a pip-installable "
+"By proactively following this convention ourselves, our module will have the"
+" same behavior when run directly (i.e. ``python echo.py``) as it will have "
+"if we later package it as a console script entry-point in a pip-installable "
 "package."
 msgstr ""
 
@@ -291,8 +292,8 @@ msgid ""
 "In particular, be careful about returning strings from your ``main`` "
 "function. :func:`sys.exit` will interpret a string argument as a failure "
 "message, so your program will have an exit code of ``1``, indicating "
-"failure, and the string will be written to :data:`sys.stderr`.  The ``echo."
-"py`` example from earlier exemplifies using the ``sys.exit(main())`` "
+"failure, and the string will be written to :data:`sys.stderr`.  The "
+"``echo.py`` example from earlier exemplifies using the ``sys.exit(main())`` "
 "convention."
 msgstr ""
 
@@ -325,8 +326,8 @@ msgstr ""
 
 #: ../../library/__main__.rst:213
 msgid ""
-"``__main__.py`` will be executed when the package itself is invoked directly "
-"from the command line using the :option:`-m` flag. For example:"
+"``__main__.py`` will be executed when the package itself is invoked directly"
+" from the command line using the :option:`-m` flag. For example:"
 msgstr ""
 
 #: ../../library/__main__.rst:216
@@ -384,8 +385,8 @@ msgstr ""
 
 #: ../../library/__main__.rst:254
 msgid ""
-"This won't work for ``__main__.py`` files in the root directory of a ``."
-"zip`` file though.  Hence, for consistency, a minimal ``__main__.py`` "
+"This won't work for ``__main__.py`` files in the root directory of a "
+"``.zip`` file though.  Hence, for consistency, a minimal ``__main__.py`` "
 "without a ``__name__`` check is preferred."
 msgstr ""
 
@@ -534,6 +535,6 @@ msgstr ""
 
 #: ../../library/__main__.rst:361
 msgid ""
-"The ``__main__`` scope is used in the implementation of :mod:`pdb` and :mod:"
-"`rlcompleter`."
+"The ``__main__`` scope is used in the implementation of :mod:`pdb` and "
+":mod:`rlcompleter`."
 msgstr ""