Skip to content

Commit 137bcd6

Browse files
author
GitHub Action's update-translation job
committed
Update translation from Transifex
1 parent 3b3907d commit 137bcd6

15 files changed

Lines changed: 218 additions & 122 deletions

File tree

‎faq/gui.po‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ msgid ""
1212
msgstr ""
1313
"Project-Id-Version: Python 3.14\n"
1414
"Report-Msgid-Bugs-To: \n"
15-
"POT-Creation-Date: 2025-09-23 14:15+0000\n"
15+
"POT-Creation-Date: 2025-10-13 14:15+0000\n"
1616
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
1717
"Last-Translator: Dennis Betz, 2025\n"
1818
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"

‎faq/windows.po‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ msgid ""
1212
msgstr ""
1313
"Project-Id-Version: Python 3.14\n"
1414
"Report-Msgid-Bugs-To: \n"
15-
"POT-Creation-Date: 2025-09-23 14:15+0000\n"
15+
"POT-Creation-Date: 2025-10-13 14:15+0000\n"
1616
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
1717
"Last-Translator: Dennis Betz, 2025\n"
1818
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"

‎glossary.po‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.14\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2025-09-23 14:15+0000\n"
14+
"POT-Creation-Date: 2025-10-13 14:15+0000\n"
1515
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
1616
"Last-Translator: python-doc bot, 2025\n"
1717
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"

‎howto/a-conceptual-overview-of-asyncio.po‎

Lines changed: 36 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ msgid ""
88
msgstr ""
99
"Project-Id-Version: Python 3.14\n"
1010
"Report-Msgid-Bugs-To: \n"
11-
"POT-Creation-Date: 2025-10-05 14:11+0000\n"
11+
"POT-Creation-Date: 2025-10-15 14:16+0000\n"
1212
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
1313
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
1414
"MIME-Version: 1.0\n"
@@ -27,15 +27,15 @@ msgid ""
2727
msgstr ""
2828

2929
msgid ""
30-
"You might be curious about some key :mod:`!asyncio` concepts. You'll be "
31-
"comfortably able to answer these questions by the end of this article:"
30+
"You might be curious about some key :mod:`!asyncio` concepts. By the end of "
31+
"this article, you'll be able to comfortably answer these questions:"
3232
msgstr ""
3333

3434
msgid "What's happening behind the scenes when an object is awaited?"
3535
msgstr ""
3636

3737
msgid ""
38-
"How does :mod:`!asyncio` differentiate between a task which doesn't need CPU-"
38+
"How does :mod:`!asyncio` differentiate between a task which doesn't need CPU "
3939
"time (such as a network request or file read) as opposed to a task that does "
4040
"(such as computing n-factorial)?"
4141
msgstr ""
@@ -67,7 +67,7 @@ msgstr ""
6767

6868
msgid ""
6969
"In part 1, we'll cover the main, high-level building blocks of :mod:`!"
70-
"asyncio`: the event loop, coroutine functions, coroutine objects, tasks and "
70+
"asyncio`: the event loop, coroutine functions, coroutine objects, tasks, and "
7171
"``await``."
7272
msgstr ""
7373

@@ -91,7 +91,7 @@ msgid ""
9191
"event loop will then select another job from its pool and invoke it. You can "
9292
"*roughly* think of the collection of jobs as a queue: jobs are added and "
9393
"then processed one at a time, generally (but not always) in order. This "
94-
"process repeats indefinitely with the event loop cycling endlessly onwards. "
94+
"process repeats indefinitely, with the event loop cycling endlessly onwards. "
9595
"If there are no more jobs pending execution, the event loop is smart enough "
9696
"to rest and avoid needlessly wasting CPU cycles, and will come back when "
9797
"there's more work to be done."
@@ -356,7 +356,7 @@ msgstr ""
356356
msgid ""
357357
"Generally speaking, when the awaited task finishes (``dig_the_hole_task``), "
358358
"the original task or coroutine (``plant_a_tree()``) is added back to the "
359-
"event loops to-do list to be resumed."
359+
"event loop's to-do list to be resumed."
360360
msgstr ""
361361

362362
msgid ""
@@ -394,7 +394,7 @@ msgstr ""
394394
msgid ""
395395
"The first statement in the coroutine ``main()`` creates ``task_b`` and "
396396
"schedules it for execution via the event loop. Then, ``coro_a()`` is "
397-
"repeatedly awaited. Control never cedes to the event loop which is why we "
397+
"repeatedly awaited. Control never cedes to the event loop, which is why we "
398398
"see the output of all three ``coro_a()`` invocations before ``coro_b()``'s "
399399
"output:"
400400
msgstr ""
@@ -425,18 +425,18 @@ msgid ""
425425
"This behavior of ``await coroutine`` can trip a lot of people up! That "
426426
"example highlights how using only ``await coroutine`` could unintentionally "
427427
"hog control from other tasks and effectively stall the event loop. :func:"
428-
"`asyncio.run` can help you detect such occurences via the ``debug=True`` "
429-
"flag which accordingly enables :ref:`debug mode <asyncio-debug-mode>`. Among "
430-
"other things, it will log any coroutines that monopolize execution for 100ms "
431-
"or longer."
428+
"`asyncio.run` can help you detect such occurrences via the ``debug=True`` "
429+
"flag, which enables :ref:`debug mode <asyncio-debug-mode>`. Among other "
430+
"things, it will log any coroutines that monopolize execution for 100ms or "
431+
"longer."
432432
msgstr ""
433433

434434
msgid ""
435435
"The design intentionally trades off some conceptual clarity around usage of "
436436
"``await`` for improved performance. Each time a task is awaited, control "
437437
"needs to be passed all the way up the call stack to the event loop. That "
438-
"might sound minor, but in a large program with many ``await``'s and a deep "
439-
"callstack that overhead can add up to a meaningful performance drag."
438+
"might sound minor, but in a large program with many ``await`` statements and "
439+
"a deep call stack, that overhead can add up to a meaningful performance drag."
440440
msgstr ""
441441

442442
msgid "A conceptual overview part 2: the nuts and bolts"
@@ -460,7 +460,7 @@ msgid ""
460460
"resume a coroutine. If the coroutine was paused and is now being resumed, "
461461
"the argument ``arg`` will be sent in as the return value of the ``yield`` "
462462
"statement which originally paused it. If the coroutine is being used for the "
463-
"first time (as opposed to being resumed) ``arg`` must be ``None``."
463+
"first time (as opposed to being resumed), ``arg`` must be ``None``."
464464
msgstr ""
465465

466466
msgid ""
@@ -492,12 +492,12 @@ msgid ""
492492
msgstr ""
493493

494494
msgid ""
495-
":ref:`yield <yieldexpr>`, like usual, pauses execution and returns control "
496-
"to the caller. In the example above, the ``yield``, on line 3, is called by "
495+
":ref:`yield <yieldexpr>`, as usual, pauses execution and returns control to "
496+
"the caller. In the example above, the ``yield``, on line 3, is called by "
497497
"``... = await rock`` on line 11. More broadly speaking, ``await`` calls the :"
498498
"meth:`~object.__await__` method of the given object. ``await`` also does one "
499499
"more very special thing: it propagates (or \"passes along\") any ``yield``\\ "
500-
"s it receives up the call-chain. In this case, that's back to ``... = "
500+
"s it receives up the call chain. In this case, that's back to ``... = "
501501
"coroutine.send(None)`` on line 16."
502502
msgstr ""
503503

@@ -561,12 +561,12 @@ msgid ""
561561
msgstr ""
562562

563563
msgid ""
564-
"A future has a few important attributes. One is its state which can be "
565-
"either \"pending\", \"cancelled\" or \"done\". Another is its result, which "
564+
"A future has a few important attributes. One is its state, which can be "
565+
"either \"pending\", \"cancelled\", or \"done\". Another is its result, which "
566566
"is set when the state transitions to done. Unlike a coroutine, a future does "
567567
"not represent the actual computation to be done; instead, it represents the "
568568
"status and result of that computation, kind of like a status light (red, "
569-
"yellow or green) or indicator."
569+
"yellow, or green) or indicator."
570570
msgstr ""
571571

572572
msgid ""
@@ -593,10 +593,10 @@ msgid ""
593593
msgstr ""
594594

595595
msgid ""
596-
"This snippet registers a few tasks with the event loop and then awaits a "
597-
"coroutine wrapped in a task: ``async_sleep(3)``. We want that task to finish "
598-
"only after three seconds have elapsed, but without preventing other tasks "
599-
"from running."
596+
"This snippet registers a few tasks with the event loop and then awaits the "
597+
"task created by ``asyncio.create_task``, which wraps the ``async_sleep(3)`` "
598+
"coroutine. We want that task to finish only after three seconds have "
599+
"elapsed, but without preventing other tasks from running."
600600
msgstr ""
601601

602602
msgid ""
@@ -645,8 +645,8 @@ msgid ""
645645
msgstr ""
646646

647647
msgid ""
648-
"Below, we'll use a rather bare object, ``YieldToEventLoop()``, to ``yield`` "
649-
"from ``__await__`` in order to cede control to the event loop. This is "
648+
"Below, we use a rather bare ``YieldToEventLoop()`` object to ``yield`` from "
649+
"its ``__await__`` method, ceding control to the event loop. This is "
650650
"effectively the same as calling ``asyncio.sleep(0)``, but this approach "
651651
"offers more clarity, not to mention it's somewhat cheating to use ``asyncio."
652652
"sleep`` when showcasing how to implement it!"
@@ -658,12 +658,12 @@ msgid ""
658658
"which runs the coroutine ``_sleep_watcher(...)``, will be invoked once per "
659659
"full cycle of the event loop. On each resumption, it'll check the time and "
660660
"if not enough has elapsed, then it'll pause once again and hand control back "
661-
"to the event loop. Eventually, enough time will have elapsed, and "
662-
"``_sleep_watcher(...)`` will mark the future as done, and then itself finish "
663-
"too by breaking out of the infinite ``while`` loop. Given this helper task "
664-
"is only invoked once per cycle of the event loop, you'd be correct to note "
665-
"that this asynchronous sleep will sleep *at least* three seconds, rather "
666-
"than exactly three seconds. Note this is also of true of ``asyncio.sleep``."
661+
"to the event loop. Once enough time has elapsed, ``_sleep_watcher(...)`` "
662+
"marks the future as done and completes by exiting its infinite ``while`` "
663+
"loop. Given this helper task is only invoked once per cycle of the event "
664+
"loop, you'd be correct to note that this asynchronous sleep will sleep *at "
665+
"least* three seconds, rather than exactly three seconds. Note this is also "
666+
"true of ``asyncio.sleep``."
667667
msgstr ""
668668

669669
msgid ""
@@ -712,7 +712,7 @@ msgid ""
712712
msgstr ""
713713

714714
msgid ""
715-
"But, that's all for now. Hopefully you're ready to more confidently dive "
716-
"into some async programming or check out advanced topics in the :mod:`rest "
717-
"of the documentation <asyncio>`."
715+
"But that's all for now. Hopefully you're ready to more confidently dive into "
716+
"some async programming or check out advanced topics in the :mod:`rest of the "
717+
"documentation <asyncio>`."
718718
msgstr ""

‎library/cmath.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.14\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2025-10-05 14:11+0000\n"
14+
"POT-Creation-Date: 2025-10-15 14:16+0000\n"
1515
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
1616
"Last-Translator: python-doc bot, 2025\n"
1717
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
@@ -477,7 +477,7 @@ msgstr ""
477477

478478
msgid ""
479479
"A floating-point \"not a number\" (NaN) value. Equivalent to "
480-
"``float('nan')``."
480+
"``float('nan')``. See also :data:`math.nan`."
481481
msgstr ""
482482

483483
msgid ""

‎library/cmdline.po‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.14\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2025-09-23 14:15+0000\n"
14+
"POT-Creation-Date: 2025-10-13 14:15+0000\n"
1515
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
1616
"Last-Translator: python-doc bot, 2025\n"
1717
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"

‎library/http.po‎

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ msgid ""
88
msgstr ""
99
"Project-Id-Version: Python 3.14\n"
1010
"Report-Msgid-Bugs-To: \n"
11-
"POT-Creation-Date: 2025-10-05 14:11+0000\n"
11+
"POT-Creation-Date: 2025-10-15 14:16+0000\n"
1212
"PO-Revision-Date: 2025-09-16 00:01+0000\n"
1313
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
1414
"MIME-Version: 1.0\n"
@@ -667,7 +667,9 @@ msgstr ""
667667

668668
msgid ""
669669
"Implemented RFC9110 naming for status constants. Old constant names are "
670-
"preserved for backwards compatibility."
670+
"preserved for backwards compatibility: ``413 REQUEST_ENTITY_TOO_LARGE``, "
671+
"``414 REQUEST_URI_TOO_LONG``, ``416 REQUESTED_RANGE_NOT_SATISFIABLE`` and "
672+
"``422 UNPROCESSABLE_ENTITY``."
671673
msgstr ""
672674

673675
msgid "HTTP status category"

‎library/smtplib.po‎

Lines changed: 47 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ msgid ""
88
msgstr ""
99
"Project-Id-Version: Python 3.14\n"
1010
"Report-Msgid-Bugs-To: \n"
11-
"POT-Creation-Date: 2025-10-05 14:11+0000\n"
11+
"POT-Creation-Date: 2025-10-15 14:16+0000\n"
1212
"PO-Revision-Date: 2025-09-16 00:01+0000\n"
1313
"Language-Team: German (https://app.transifex.com/python-doc/teams/5390/de/)\n"
1414
"MIME-Version: 1.0\n"
@@ -100,14 +100,14 @@ msgstr ""
100100
msgid ""
101101
"An :class:`SMTP_SSL` instance behaves exactly the same as instances of :"
102102
"class:`SMTP`. :class:`SMTP_SSL` should be used for situations where SSL is "
103-
"required from the beginning of the connection and using :meth:`starttls` is "
104-
"not appropriate. If *host* is not specified, the local host is used. If "
105-
"*port* is zero, the standard SMTP-over-SSL port (465) is used. The optional "
106-
"arguments *local_hostname*, *timeout* and *source_address* have the same "
107-
"meaning as they do in the :class:`SMTP` class. *context*, also optional, "
108-
"can contain a :class:`~ssl.SSLContext` and allows configuring various "
109-
"aspects of the secure connection. Please read :ref:`ssl-security` for best "
110-
"practices."
103+
"required from the beginning of the connection and using :meth:`~SMTP."
104+
"starttls` is not appropriate. If *host* is not specified, the local host is "
105+
"used. If *port* is zero, the standard SMTP-over-SSL port (465) is used. The "
106+
"optional arguments *local_hostname*, *timeout* and *source_address* have the "
107+
"same meaning as they do in the :class:`SMTP` class. *context*, also "
108+
"optional, can contain a :class:`~ssl.SSLContext` and allows configuring "
109+
"various aspects of the secure connection. Please read :ref:`ssl-security` "
110+
"for best practices."
111111
msgstr ""
112112

113113
msgid "*context* was added."
@@ -132,10 +132,10 @@ msgstr ""
132132
msgid ""
133133
"The LMTP protocol, which is very similar to ESMTP, is heavily based on the "
134134
"standard SMTP client. It's common to use Unix sockets for LMTP, so our :meth:"
135-
"`connect` method must support that as well as a regular host:port server. "
136-
"The optional arguments *local_hostname* and *source_address* have the same "
137-
"meaning as they do in the :class:`SMTP` class. To specify a Unix socket, you "
138-
"must use an absolute path for *host*, starting with a '/'."
135+
"`~SMTP.connect` method must support that as well as a regular host:port "
136+
"server. The optional arguments *local_hostname* and *source_address* have "
137+
"the same meaning as they do in the :class:`SMTP` class. To specify a Unix "
138+
"socket, you must use an absolute path for *host*, starting with a '/'."
139139
msgstr ""
140140

141141
msgid ""
@@ -167,8 +167,13 @@ msgstr ""
167167
msgid ""
168168
"Base class for all exceptions that include an SMTP error code. These "
169169
"exceptions are generated in some instances when the SMTP server returns an "
170-
"error code. The error code is stored in the :attr:`smtp_code` attribute of "
171-
"the error, and the :attr:`smtp_error` attribute is set to the error message."
170+
"error code."
171+
msgstr ""
172+
173+
msgid "The error code."
174+
msgstr ""
175+
176+
msgid "The error message."
172177
msgstr ""
173178

174179
msgid ""
@@ -177,10 +182,12 @@ msgid ""
177182
"the SMTP server refused."
178183
msgstr ""
179184

185+
msgid "All recipient addresses refused."
186+
msgstr ""
187+
180188
msgid ""
181-
"All recipient addresses refused. The errors for each recipient are "
182-
"accessible through the attribute :attr:`recipients`, which is a dictionary "
183-
"of exactly the same sort as :meth:`SMTP.sendmail` returns."
189+
"A dictionary of exactly the same sort as returned by :meth:`SMTP.sendmail` "
190+
"containing the errors for each recipient."
184191
msgstr ""
185192

186193
msgid "The SMTP server refused to accept the message data."
@@ -455,7 +462,7 @@ msgid "SSL/TLS support is not available to your Python interpreter."
455462
msgstr ""
456463

457464
msgid ""
458-
"The method now supports hostname check with :attr:`SSLContext."
465+
"The method now supports hostname check with :attr:`ssl.SSLContext."
459466
"check_hostname` and *Server Name Indicator* (see :const:`~ssl.HAS_SNI`)."
460467
msgstr ""
461468

@@ -472,7 +479,7 @@ msgid ""
472479
"*mail_options*. ESMTP options (such as ``DSN`` commands) that should be used "
473480
"with all ``RCPT`` commands can be passed as *rcpt_options*. (If you need to "
474481
"use different ESMTP options to different recipients you have to use the low-"
475-
"level methods such as :meth:`mail`, :meth:`rcpt` and :meth:`data` to send "
482+
"level methods such as :meth:`!mail`, :meth:`!rcpt` and :meth:`!data` to send "
476483
"the message.)"
477484
msgstr ""
478485

@@ -517,11 +524,7 @@ msgstr ""
517524
msgid ":exc:`SMTPRecipientsRefused`"
518525
msgstr ""
519526

520-
msgid ""
521-
"All recipients were refused. Nobody got the mail. The :attr:`recipients` "
522-
"attribute of the exception object is a dictionary with information about the "
523-
"refused recipients (like the one returned when at least one recipient was "
524-
"accepted)."
527+
msgid "All recipients were refused. Nobody got the mail."
525528
msgstr ""
526529

527530
msgid ":exc:`SMTPSenderRefused`"
@@ -606,6 +609,25 @@ msgid ""
606609
"documented here. For details, consult the module code."
607610
msgstr ""
608611

612+
msgid "Additionally, an SMTP instance has the following attributes:"
613+
msgstr ""
614+
615+
msgid "The response to the ``HELO`` command, see :meth:`helo`."
616+
msgstr ""
617+
618+
msgid "The response to the ``EHLO`` command, see :meth:`ehlo`."
619+
msgstr ""
620+
621+
msgid ""
622+
"A boolean value indicating whether the server supports ESMTP, see :meth:"
623+
"`ehlo`."
624+
msgstr ""
625+
626+
msgid ""
627+
"A dictionary of the names of SMTP service extensions supported by the "
628+
"server, see :meth:`ehlo`."
629+
msgstr ""
630+
609631
msgid "SMTP Example"
610632
msgstr ""
611633

0 commit comments

Comments
 (0)