Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit374f65f

Browse files
author
GitHub Action's update-translation job
committed
Update translation from Transifex
1 parentacb8d1c commit374f65f

File tree

11 files changed

+214
-118
lines changed

11 files changed

+214
-118
lines changed

‎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:Hungarian (https://app.transifex.com/python-doc/teams/5390/"
1414
"hu/)\n"
@@ -28,15 +28,15 @@ msgid ""
2828
msgstr""
2929

3030
msgid""
31-
"You might be curious about some key :mod:`!asyncio` concepts.You'll be "
32-
"comfortablyable to answer these questions by the end of this article:"
31+
"You might be curious about some key :mod:`!asyncio` concepts.By the end of "
32+
"this article, you'll beable tocomfortablyanswer these questions:"
3333
msgstr""
3434

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

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

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

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

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

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

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

467467
msgid""
@@ -493,12 +493,12 @@ msgid ""
493493
msgstr""
494494

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

@@ -562,12 +562,12 @@ msgid ""
562562
msgstr""
563563

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

573573
msgid""
@@ -594,10 +594,10 @@ msgid ""
594594
msgstr""
595595

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

603603
msgid""
@@ -646,8 +646,8 @@ msgid ""
646646
msgstr""
647647

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

670670
msgid""
@@ -713,7 +713,7 @@ msgid ""
713713
msgstr""
714714

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

‎library/cmath.po‎

Lines changed: 2 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:00+0000\n"
1313
"Language-Team:Hungarian (https://app.transifex.com/python-doc/teams/5390/"
1414
"hu/)\n"
@@ -474,7 +474,7 @@ msgstr ""
474474

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

480480
msgid""

‎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:Hungarian (https://app.transifex.com/python-doc/teams/5390/"
1414
"hu/)\n"
@@ -668,7 +668,9 @@ msgstr ""
668668

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

674676
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:Hungarian (https://app.transifex.com/python-doc/teams/5390/"
1414
"hu/)\n"
@@ -101,14 +101,14 @@ msgstr ""
101101
msgid""
102102
"An :class:`SMTP_SSL` instance behaves exactly the same as instances of :"
103103
"class:`SMTP`. :class:`SMTP_SSL` should be used for situations where SSL is "
104-
"required from the beginning of the connection and using :meth:`starttls` is"
105-
"not appropriate. If *host* is not specified, the local host is used. If "
106-
"*port* is zero, the standard SMTP-over-SSL port (465) is used. The optional "
107-
"arguments *local_hostname*, *timeout* and *source_address* have the same "
108-
"meaning as they do in the :class:`SMTP` class. *context*, also optional, "
109-
"can contain a :class:`~ssl.SSLContext` and allows configuring various "
110-
"aspects of the secure connection. Please read :ref:`ssl-security` for best "
111-
"practices."
104+
"required from the beginning of the connection and using :meth:`~SMTP."
105+
"starttls` isnot appropriate. If *host* is not specified, the local host is "
106+
"used. If*port* is zero, the standard SMTP-over-SSL port (465) is used. The "
107+
"optionalarguments *local_hostname*, *timeout* and *source_address* have the "
108+
"samemeaning as they do in the :class:`SMTP` class. *context*, also "
109+
"optional,can contain a :class:`~ssl.SSLContext` and allows configuring "
110+
"variousaspects of the secure connection. Please read :ref:`ssl-security` "
111+
"for bestpractices."
112112
msgstr""
113113

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

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

175180
msgid""
@@ -178,10 +183,12 @@ msgid ""
178183
"the SMTP server refused."
179184
msgstr""
180185

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

187194
msgid"The SMTP server refused to accept the message data."
@@ -456,7 +463,7 @@ msgid "SSL/TLS support is not available to your Python interpreter."
456463
msgstr""
457464

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

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

@@ -518,11 +525,7 @@ msgstr ""
518525
msgid":exc:`SMTPRecipientsRefused`"
519526
msgstr""
520527

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

528531
msgid":exc:`SMTPSenderRefused`"
@@ -607,6 +610,25 @@ msgid ""
607610
"documented here. For details, consult the module code."
608611
msgstr""
609612

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

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp