Update translation from Transifex

Author: GitHub Action's update-translation job

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

@@ -8,7 +8,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-10-05 14:11+0000\n"
+"POT-Creation-Date: 2025-10-15 14:16+0000\n"
 "PO-Revision-Date: 2025-09-16 00:00+0000\n"
 "Language-Team: Indonesian (https://app.transifex.com/python-doc/teams/5390/"
 "id/)\n"
@@ -28,15 +28,15 @@ msgid ""
 msgstr ""
 
 msgid ""
-"You might be curious about some key :mod:`!asyncio` concepts. You'll be "
-"comfortably able to answer these questions by the end of this article:"
+"You might be curious about some key :mod:`!asyncio` concepts. By the end of "
+"this article, you'll be able to comfortably answer these questions:"
 msgstr ""
 
 msgid "What's happening behind the scenes when an object is awaited?"
 msgstr ""
 
 msgid ""
-"How does :mod:`!asyncio` differentiate between a task which doesn't need CPU-"
+"How does :mod:`!asyncio` differentiate between a task which doesn't need CPU "
 "time (such as a network request or file read) as opposed to a task that does "
 "(such as computing n-factorial)?"
 msgstr ""
@@ -68,7 +68,7 @@ msgstr ""
 
 msgid ""
 "In part 1, we'll cover the main, high-level building blocks of :mod:`!"
-"asyncio`: the event loop, coroutine functions, coroutine objects, tasks and "
+"asyncio`: the event loop, coroutine functions, coroutine objects, tasks, and "
 "``await``."
 msgstr ""
 
@@ -92,7 +92,7 @@ msgid ""
 "event loop will then select another job from its pool and invoke it. You can "
 "*roughly* think of the collection of jobs as a queue: jobs are added and "
 "then processed one at a time, generally (but not always) in order. This "
-"process repeats indefinitely with the event loop cycling endlessly onwards. "
+"process repeats indefinitely, with the event loop cycling endlessly onwards. "
 "If there are no more jobs pending execution, the event loop is smart enough "
 "to rest and avoid needlessly wasting CPU cycles, and will come back when "
 "there's more work to be done."
@@ -357,7 +357,7 @@ msgstr ""
 msgid ""
 "Generally speaking, when the awaited task finishes (``dig_the_hole_task``), "
 "the original task or coroutine (``plant_a_tree()``) is added back to the "
-"event loops to-do list to be resumed."
+"event loop's to-do list to be resumed."
 msgstr ""
 
 msgid ""
@@ -395,7 +395,7 @@ msgstr ""
 msgid ""
 "The first statement in the coroutine ``main()`` creates ``task_b`` and "
 "schedules it for execution via the event loop. Then, ``coro_a()`` is "
-"repeatedly awaited. Control never cedes to the event loop which is why we "
+"repeatedly awaited. Control never cedes to the event loop, which is why we "
 "see the output of all three ``coro_a()`` invocations before ``coro_b()``'s "
 "output:"
 msgstr ""
@@ -426,18 +426,18 @@ msgid ""
 "This behavior of ``await coroutine`` can trip a lot of people up! That "
 "example highlights how using only ``await coroutine`` could unintentionally "
 "hog control from other tasks and effectively stall the event loop. :func:"
-"`asyncio.run` can help you detect such occurences via the ``debug=True`` "
-"flag which accordingly enables :ref:`debug mode <asyncio-debug-mode>`. Among "
-"other things, it will log any coroutines that monopolize execution for 100ms "
-"or longer."
+"`asyncio.run` can help you detect such occurrences via the ``debug=True`` "
+"flag, which enables :ref:`debug mode <asyncio-debug-mode>`. Among other "
+"things, it will log any coroutines that monopolize execution for 100ms or "
+"longer."
 msgstr ""
 
 msgid ""
 "The design intentionally trades off some conceptual clarity around usage of "
 "``await`` for improved performance. Each time a task is awaited, control "
 "needs to be passed all the way up the call stack to the event loop. That "
-"might sound minor, but in a large program with many ``await``'s and a deep "
-"callstack that overhead can add up to a meaningful performance drag."
+"might sound minor, but in a large program with many ``await`` statements and "
+"a deep call stack, that overhead can add up to a meaningful performance drag."
 msgstr ""
 
 msgid "A conceptual overview part 2: the nuts and bolts"
@@ -461,7 +461,7 @@ msgid ""
 "resume a coroutine. If the coroutine was paused and is now being resumed, "
 "the argument ``arg`` will be sent in as the return value of the ``yield`` "
 "statement which originally paused it. If the coroutine is being used for the "
-"first time (as opposed to being resumed) ``arg`` must be ``None``."
+"first time (as opposed to being resumed), ``arg`` must be ``None``."
 msgstr ""
 
 msgid ""
@@ -493,12 +493,12 @@ msgid ""
 msgstr ""
 
 msgid ""
-":ref:`yield <yieldexpr>`, like usual, pauses execution and returns control "
-"to the caller. In the example above, the ``yield``, on line 3, is called by "
+":ref:`yield <yieldexpr>`, as usual, pauses execution and returns control to "
+"the caller. In the example above, the ``yield``, on line 3, is called by "
 "``... = await rock`` on line 11. More broadly speaking, ``await`` calls the :"
 "meth:`~object.__await__` method of the given object. ``await`` also does one "
 "more very special thing: it propagates (or \"passes along\") any ``yield``\\ "
-"s it receives up the call-chain. In this case, that's back to ``... = "
+"s it receives up the call chain. In this case, that's back to ``... = "
 "coroutine.send(None)`` on line 16."
 msgstr ""
 
@@ -562,12 +562,12 @@ msgid ""
 msgstr ""
 
 msgid ""
-"A future has a few important attributes. One is its state which can be "
-"either \"pending\", \"cancelled\" or \"done\". Another is its result, which "
+"A future has a few important attributes. One is its state, which can be "
+"either \"pending\", \"cancelled\", or \"done\". Another is its result, which "
 "is set when the state transitions to done. Unlike a coroutine, a future does "
 "not represent the actual computation to be done; instead, it represents the "
 "status and result of that computation, kind of like a status light (red, "
-"yellow or green) or indicator."
+"yellow, or green) or indicator."
 msgstr ""
 
 msgid ""
@@ -594,10 +594,10 @@ msgid ""
 msgstr ""
 
 msgid ""
-"This snippet registers a few tasks with the event loop and then awaits a "
-"coroutine wrapped in a task: ``async_sleep(3)``. We want that task to finish "
-"only after three seconds have elapsed, but without preventing other tasks "
-"from running."
+"This snippet registers a few tasks with the event loop and then awaits the "
+"task created by ``asyncio.create_task``, which wraps the ``async_sleep(3)`` "
+"coroutine. We want that task to finish only after three seconds have "
+"elapsed, but without preventing other tasks from running."
 msgstr ""
 
 msgid ""
@@ -646,8 +646,8 @@ msgid ""
 msgstr ""
 
 msgid ""
-"Below, we'll use a rather bare object, ``YieldToEventLoop()``, to ``yield`` "
-"from ``__await__`` in order to cede control to the event loop. This is "
+"Below, we use a rather bare ``YieldToEventLoop()`` object to ``yield`` from "
+"its ``__await__`` method, ceding control to the event loop. This is "
 "effectively the same as calling ``asyncio.sleep(0)``, but this approach "
 "offers more clarity, not to mention it's somewhat cheating to use ``asyncio."
 "sleep`` when showcasing how to implement it!"
@@ -659,12 +659,12 @@ msgid ""
 "which runs the coroutine ``_sleep_watcher(...)``, will be invoked once per "
 "full cycle of the event loop. On each resumption, it'll check the time and "
 "if not enough has elapsed, then it'll pause once again and hand control back "
-"to the event loop. Eventually, enough time will have elapsed, and "
-"``_sleep_watcher(...)`` will mark the future as done, and then itself finish "
-"too by breaking out of the infinite ``while`` loop. Given this helper task "
-"is only invoked once per cycle of the event loop, you'd be correct to note "
-"that this asynchronous sleep will sleep *at least* three seconds, rather "
-"than exactly three seconds. Note this is also of true of ``asyncio.sleep``."
+"to the event loop. Once enough time has elapsed, ``_sleep_watcher(...)`` "
+"marks the future as done and completes by exiting its infinite ``while`` "
+"loop. Given this helper task is only invoked once per cycle of the event "
+"loop, you'd be correct to note that this asynchronous sleep will sleep *at "
+"least* three seconds, rather than exactly three seconds. Note this is also "
+"true of ``asyncio.sleep``."
 msgstr ""
 
 msgid ""
@@ -713,7 +713,7 @@ msgid ""
 msgstr ""
 
 msgid ""
-"But, that's all for now. Hopefully you're ready to more confidently dive "
-"into some async programming or check out advanced topics in the :mod:`rest "
-"of the documentation <asyncio>`."
+"But that's all for now. Hopefully you're ready to more confidently dive into "
+"some async programming or check out advanced topics in the :mod:`rest of the "
+"documentation <asyncio>`."
 msgstr ""

library/cmath.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-10-05 14:11+0000\n"
+"POT-Creation-Date: 2025-10-15 14:16+0000\n"
 "PO-Revision-Date: 2025-09-16 00:00+0000\n"
 "Last-Translator: python-doc bot, 2025\n"
 "Language-Team: Indonesian (https://app.transifex.com/python-doc/teams/5390/"
@@ -478,7 +478,7 @@ msgstr ""
 
 msgid ""
 "A floating-point \"not a number\" (NaN) value.  Equivalent to "
-"``float('nan')``."
+"``float('nan')``. See also :data:`math.nan`."
 msgstr ""
 
 msgid ""

library/http.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-10-05 14:11+0000\n"
+"POT-Creation-Date: 2025-10-15 14:16+0000\n"
 "PO-Revision-Date: 2025-09-16 00:01+0000\n"
 "Last-Translator: python-doc bot, 2025\n"
 "Language-Team: Indonesian (https://app.transifex.com/python-doc/teams/5390/"
@@ -672,7 +672,9 @@ msgstr ""
 
 msgid ""
 "Implemented RFC9110 naming for status constants. Old constant names are "
-"preserved for backwards compatibility."
+"preserved for backwards compatibility: ``413 REQUEST_ENTITY_TOO_LARGE``, "
+"``414 REQUEST_URI_TOO_LONG``, ``416 REQUESTED_RANGE_NOT_SATISFIABLE`` and "
+"``422 UNPROCESSABLE_ENTITY``."
 msgstr ""
 
 msgid "HTTP status category"

library/smtplib.po

@@ -11,7 +11,7 @@ msgid ""
 msgstr ""
 "Project-Id-Version: Python 3.14\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2025-10-05 14:11+0000\n"
+"POT-Creation-Date: 2025-10-15 14:16+0000\n"
 "PO-Revision-Date: 2025-09-16 00:01+0000\n"
 "Last-Translator: python-doc bot, 2025\n"
 "Language-Team: Indonesian (https://app.transifex.com/python-doc/teams/5390/"
@@ -105,14 +105,14 @@ msgstr ""
 msgid ""
 "An :class:`SMTP_SSL` instance behaves exactly the same as instances of :"
 "class:`SMTP`. :class:`SMTP_SSL` should be used for situations where SSL is "
-"required from the beginning of the connection and using :meth:`starttls` is "
-"not appropriate. If *host* is not specified, the local host is used. If "
-"*port* is zero, the standard SMTP-over-SSL port (465) is used.  The optional "
-"arguments *local_hostname*, *timeout* and *source_address* have the same "
-"meaning as they do in the :class:`SMTP` class.  *context*, also optional, "
-"can contain a :class:`~ssl.SSLContext` and allows configuring various "
-"aspects of the secure connection.  Please read :ref:`ssl-security` for best "
-"practices."
+"required from the beginning of the connection and using :meth:`~SMTP."
+"starttls` is not appropriate. If *host* is not specified, the local host is "
+"used. If *port* is zero, the standard SMTP-over-SSL port (465) is used.  The "
+"optional arguments *local_hostname*, *timeout* and *source_address* have the "
+"same meaning as they do in the :class:`SMTP` class.  *context*, also "
+"optional, can contain a :class:`~ssl.SSLContext` and allows configuring "
+"various aspects of the secure connection.  Please read :ref:`ssl-security` "
+"for best practices."
 msgstr ""
 
 msgid "*context* was added."
@@ -137,10 +137,10 @@ msgstr ""
 msgid ""
 "The LMTP protocol, which is very similar to ESMTP, is heavily based on the "
 "standard SMTP client. It's common to use Unix sockets for LMTP, so our :meth:"
-"`connect` method must support that as well as a regular host:port server. "
-"The optional arguments *local_hostname* and *source_address* have the same "
-"meaning as they do in the :class:`SMTP` class. To specify a Unix socket, you "
-"must use an absolute path for *host*, starting with a '/'."
+"`~SMTP.connect` method must support that as well as a regular host:port "
+"server. The optional arguments *local_hostname* and *source_address* have "
+"the same meaning as they do in the :class:`SMTP` class. To specify a Unix "
+"socket, you must use an absolute path for *host*, starting with a '/'."
 msgstr ""
 
 msgid ""
@@ -172,8 +172,13 @@ msgstr ""
 msgid ""
 "Base class for all exceptions that include an SMTP error code. These "
 "exceptions are generated in some instances when the SMTP server returns an "
-"error code.  The error code is stored in the :attr:`smtp_code` attribute of "
-"the error, and the :attr:`smtp_error` attribute is set to the error message."
+"error code."
+msgstr ""
+
+msgid "The error code."
+msgstr "Kode errornya"
+
+msgid "The error message."
 msgstr ""
 
 msgid ""
@@ -182,10 +187,12 @@ msgid ""
 "the SMTP server refused."
 msgstr ""
 
+msgid "All recipient addresses refused."
+msgstr ""
+
 msgid ""
-"All recipient addresses refused.  The errors for each recipient are "
-"accessible through the attribute :attr:`recipients`, which is a dictionary "
-"of exactly the same sort as :meth:`SMTP.sendmail` returns."
+"A dictionary of exactly the same sort as returned by :meth:`SMTP.sendmail` "
+"containing the errors for each recipient."
 msgstr ""
 
 msgid "The SMTP server refused to accept the message data."
@@ -460,7 +467,7 @@ msgid "SSL/TLS support is not available to your Python interpreter."
 msgstr ""
 
 msgid ""
-"The method now supports hostname check with :attr:`SSLContext."
+"The method now supports hostname check with :attr:`ssl.SSLContext."
 "check_hostname` and *Server Name Indicator* (see :const:`~ssl.HAS_SNI`)."
 msgstr ""
 
@@ -477,7 +484,7 @@ msgid ""
 "*mail_options*. ESMTP options (such as ``DSN`` commands) that should be used "
 "with all ``RCPT`` commands can be passed as *rcpt_options*.  (If you need to "
 "use different ESMTP options to different recipients you have to use the low-"
-"level methods such as :meth:`mail`, :meth:`rcpt` and :meth:`data` to send "
+"level methods such as :meth:`!mail`, :meth:`!rcpt` and :meth:`!data` to send "
 "the message.)"
 msgstr ""
 
@@ -522,11 +529,7 @@ msgstr ""
 msgid ":exc:`SMTPRecipientsRefused`"
 msgstr ""
 
-msgid ""
-"All recipients were refused.  Nobody got the mail.  The :attr:`recipients` "
-"attribute of the exception object is a dictionary with information about the "
-"refused recipients (like the one returned when at least one recipient was "
-"accepted)."
+msgid "All recipients were refused.  Nobody got the mail."
 msgstr ""
 
 msgid ":exc:`SMTPSenderRefused`"
@@ -611,6 +614,25 @@ msgid ""
 "documented here.  For details, consult the module code."
 msgstr ""
 
+msgid "Additionally, an SMTP instance has the following attributes:"
+msgstr ""
+
+msgid "The response to the ``HELO`` command, see :meth:`helo`."
+msgstr ""
+
+msgid "The response to the ``EHLO`` command, see :meth:`ehlo`."
+msgstr ""
+
+msgid ""
+"A boolean value indicating whether the server supports ESMTP, see :meth:"
+"`ehlo`."
+msgstr ""
+
+msgid ""
+"A dictionary of the names of SMTP service extensions supported by the "
+"server, see :meth:`ehlo`."
+msgstr ""
+
 msgid "SMTP Example"
 msgstr ""