Repository navigation
Expand file tree
/
Copy pathasyncio-dev.po
More file actions
225 lines (183 loc) · 6.78 KB
/
Copy pathasyncio-dev.po
File metadata and controls
225 lines (183 loc) · 6.78 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2026, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# python-doc bot, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.10\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-10-01 23:56+0000\n"
"PO-Revision-Date: 2025-09-22 15:57+0000\n"
"Last-Translator: python-doc bot, 2025\n"
"Language-Team: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "
"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "
"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
msgid "Developing with asyncio"
msgstr ""
msgid ""
"Asynchronous programming is different from classic \"sequential\" "
"programming."
msgstr ""
msgid ""
"This page lists common mistakes and traps and explains how to avoid them."
msgstr ""
msgid "Debug Mode"
msgstr ""
msgid ""
"By default asyncio runs in production mode. In order to ease the "
"development asyncio has a *debug mode*."
msgstr ""
msgid "There are several ways to enable asyncio debug mode:"
msgstr ""
msgid "Setting the :envvar:`PYTHONASYNCIODEBUG` environment variable to ``1``."
msgstr ""
msgid "Using the :ref:`Python Development Mode <devmode>`."
msgstr ""
msgid "Passing ``debug=True`` to :func:`asyncio.run`."
msgstr ""
msgid "Calling :meth:`loop.set_debug`."
msgstr ""
msgid "In addition to enabling the debug mode, consider also:"
msgstr ""
msgid ""
"setting the log level of the :ref:`asyncio logger <asyncio-logger>` "
"to :py:data:`logging.DEBUG`, for example the following snippet of code can "
"be run at startup of the application::"
msgstr ""
msgid ""
"configuring the :mod:`warnings` module to display :exc:`ResourceWarning` "
"warnings. One way of doing that is by using the :option:`-W` ``default`` "
"command line option."
msgstr ""
msgid "When the debug mode is enabled:"
msgstr ""
msgid ""
"asyncio checks for :ref:`coroutines that were not awaited <asyncio-coroutine-"
"not-scheduled>` and logs them; this mitigates the \"forgotten await\" "
"pitfall."
msgstr ""
msgid ""
"Many non-threadsafe asyncio APIs (such as :meth:`loop.call_soon` "
"and :meth:`loop.call_at` methods) raise an exception if they are called from "
"a wrong thread."
msgstr ""
msgid ""
"The execution time of the I/O selector is logged if it takes too long to "
"perform an I/O operation."
msgstr ""
msgid ""
"Callbacks taking longer than 100ms are logged. "
"The :attr:`loop.slow_callback_duration` attribute can be used to set the "
"minimum execution duration in seconds that is considered \"slow\"."
msgstr ""
msgid "Concurrency and Multithreading"
msgstr ""
msgid ""
"An event loop runs in a thread (typically the main thread) and executes all "
"callbacks and Tasks in its thread. While a Task is running in the event "
"loop, no other Tasks can run in the same thread. When a Task executes an "
"``await`` expression, the running Task gets suspended, and the event loop "
"executes the next Task."
msgstr ""
msgid ""
"To schedule a :term:`callback` from another OS thread, "
"the :meth:`loop.call_soon_threadsafe` method should be used. Example::"
msgstr ""
msgid ""
"Almost all asyncio objects are not thread safe, which is typically not a "
"problem unless there is code that works with them from outside of a Task or "
"a callback. If there's a need for such code to call a low-level asyncio "
"API, the :meth:`loop.call_soon_threadsafe` method should be used, e.g.::"
msgstr ""
msgid ""
"To schedule a coroutine object from a different OS thread, "
"the :func:`run_coroutine_threadsafe` function should be used. It returns "
"a :class:`concurrent.futures.Future` to access the result::"
msgstr ""
msgid ""
"To handle signals and to execute subprocesses, the event loop must be run in "
"the main thread."
msgstr ""
msgid ""
"The :meth:`loop.run_in_executor` method can be used with "
"a :class:`concurrent.futures.ThreadPoolExecutor` to execute blocking code in "
"a different OS thread without blocking the OS thread that the event loop "
"runs in."
msgstr ""
msgid ""
"There is currently no way to schedule coroutines or callbacks directly from "
"a different process (such as one started with :mod:`multiprocessing`). "
"The :ref:`asyncio-event-loop-methods` section lists APIs that can read from "
"pipes and watch file descriptors without blocking the event loop. In "
"addition, asyncio's :ref:`Subprocess <asyncio-subprocess>` APIs provide a "
"way to start a process and communicate with it from the event loop. Lastly, "
"the aforementioned :meth:`loop.run_in_executor` method can also be used with "
"a :class:`concurrent.futures.ProcessPoolExecutor` to execute code in a "
"different process."
msgstr ""
msgid "Running Blocking Code"
msgstr ""
msgid ""
"Blocking (CPU-bound) code should not be called directly. For example, if a "
"function performs a CPU-intensive calculation for 1 second, all concurrent "
"asyncio Tasks and IO operations would be delayed by 1 second."
msgstr ""
msgid ""
"An executor can be used to run a task in a different thread or even in a "
"different process to avoid blocking the OS thread with the event loop. See "
"the :meth:`loop.run_in_executor` method for more details."
msgstr ""
msgid "Logging"
msgstr "Logowanie"
msgid ""
"asyncio uses the :mod:`logging` module and all logging is performed via the "
"``\"asyncio\"`` logger."
msgstr ""
msgid ""
"The default log level is :py:data:`logging.INFO`, which can be easily "
"adjusted::"
msgstr ""
msgid ""
"Network logging can block the event loop. It is recommended to use a "
"separate thread for handling logs or use non-blocking IO. For example, "
"see :ref:`blocking-handlers`."
msgstr ""
msgid "Detect never-awaited coroutines"
msgstr ""
msgid ""
"When a coroutine function is called, but not awaited (e.g. ``coro()`` "
"instead of ``await coro()``) or the coroutine is not scheduled "
"with :meth:`asyncio.create_task`, asyncio will emit a :exc:`RuntimeWarning`::"
msgstr ""
msgid "Output::"
msgstr ""
msgid "Output in debug mode::"
msgstr ""
msgid ""
"The usual fix is to either await the coroutine or call "
"the :meth:`asyncio.create_task` function::"
msgstr ""
msgid "Detect never-retrieved exceptions"
msgstr ""
msgid ""
"If a :meth:`Future.set_exception` is called but the Future object is never "
"awaited on, the exception would never be propagated to the user code. In "
"this case, asyncio would emit a log message when the Future object is "
"garbage collected."
msgstr ""
msgid "Example of an unhandled exception::"
msgstr ""
msgid ""
":ref:`Enable the debug mode <asyncio-debug-mode>` to get the traceback where "
"the task was created::"
msgstr ""