Repository navigation
Expand file tree
/
Copy pathasyncio-dev.po
More file actions
578 lines (494 loc) · 15.7 KB
/
Copy pathasyncio-dev.po
File metadata and controls
578 lines (494 loc) · 15.7 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
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Bhuvansh Kataria, 2026
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-07-29 15:50+0000\n"
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
"Last-Translator: Bhuvansh Kataria, 2026\n"
"Language-Team: Panjabi (Punjabi) (https://app.transifex.com/python-doc/"
"teams/5390/pa/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pa\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\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:"
"const:`logging.DEBUG`, for example the following snippet of code can be run "
"at startup of the application::"
msgstr ""
msgid "logging.basicConfig(level=logging.DEBUG)"
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 ""
"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 100 milliseconds 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 "loop.call_soon_threadsafe(callback, *args)"
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 "loop.call_soon_threadsafe(fut.cancel)"
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 ""
"async def coro_func():\n"
" return await asyncio.sleep(1, 42)\n"
"\n"
"# Later in another OS thread:\n"
"\n"
"future = asyncio.run_coroutine_threadsafe(coro_func(), loop)\n"
"# Wait for the result:\n"
"result = future.result()"
msgstr ""
msgid "To handle signals 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` or :class:`~concurrent.futures."
"InterpreterPoolExecutor` 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, including in a "
"different interpreter, 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 ""
msgid ""
"asyncio uses the :mod:`logging` module and all logging is performed via the "
"``\"asyncio\"`` logger."
msgstr ""
msgid ""
"The default log level is :py:const:`logging.INFO`, which can be easily "
"adjusted::"
msgstr ""
msgid "logging.getLogger(\"asyncio\").setLevel(logging.WARNING)"
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 ""
"import asyncio\n"
"\n"
"async def test():\n"
" print(\"never scheduled\")\n"
"\n"
"async def main():\n"
" test()\n"
"\n"
"asyncio.run(main())"
msgstr ""
msgid "Output::"
msgstr ""
msgid ""
"test.py:7: RuntimeWarning: coroutine 'test' was never awaited\n"
" test()"
msgstr ""
msgid "Output in debug mode::"
msgstr ""
msgid ""
"test.py:7: RuntimeWarning: coroutine 'test' was never awaited\n"
"Coroutine created at (most recent call last)\n"
" File \"../t.py\", line 9, in <module>\n"
" asyncio.run(main(), debug=True)\n"
"\n"
" < .. >\n"
"\n"
" File \"../t.py\", line 7, in main\n"
" test()\n"
" test()"
msgstr ""
msgid ""
"The usual fix is to either await the coroutine or call the :meth:`asyncio."
"create_task` function::"
msgstr ""
msgid ""
"async def main():\n"
" await test()"
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 ""
"import asyncio\n"
"\n"
"async def bug():\n"
" raise Exception(\"not consumed\")\n"
"\n"
"async def main():\n"
" asyncio.create_task(bug())\n"
"\n"
"asyncio.run(main())"
msgstr ""
msgid ""
"Task exception was never retrieved\n"
"future: <Task finished coro=<bug() done, defined at test.py:3>\n"
" exception=Exception('not consumed')>\n"
"\n"
"Traceback (most recent call last):\n"
" File \"test.py\", line 4, in bug\n"
" raise Exception(\"not consumed\")\n"
"Exception: not consumed"
msgstr ""
msgid ""
":ref:`Enable the debug mode <asyncio-debug-mode>` to get the traceback where "
"the task was created::"
msgstr ""
msgid "asyncio.run(main(), debug=True)"
msgstr ""
msgid ""
"Task exception was never retrieved\n"
"future: <Task finished coro=<bug() done, defined at test.py:3>\n"
" exception=Exception('not consumed') created at asyncio/tasks.py:321>\n"
"\n"
"source_traceback: Object created at (most recent call last):\n"
" File \"../t.py\", line 9, in <module>\n"
" asyncio.run(main(), debug=True)\n"
"\n"
"< .. >\n"
"\n"
"Traceback (most recent call last):\n"
" File \"../t.py\", line 4, in bug\n"
" raise Exception(\"not consumed\")\n"
"Exception: not consumed"
msgstr ""
msgid "Asynchronous generators best practices"
msgstr ""
msgid ""
"Writing correct and efficient asyncio code requires awareness of certain "
"pitfalls. This section outlines essential best practices that can save you "
"hours of debugging."
msgstr ""
msgid "Close asynchronous generators explicitly"
msgstr ""
msgid ""
"It is recommended to manually close the :term:`asynchronous generator "
"<asynchronous generator iterator>`. If a generator exits early - for "
"example, due to an exception raised in the body of an ``async for`` loop - "
"its asynchronous cleanup code may run in an unexpected context. This can "
"occur after the tasks it depends on have completed, or during the event loop "
"shutdown when the async-generator's garbage collection hook is called."
msgstr ""
msgid ""
"To avoid this, explicitly close the generator by calling its :meth:`~agen."
"aclose` method, or use the :func:`contextlib.aclosing` context manager::"
msgstr ""
msgid ""
"import asyncio\n"
"import contextlib\n"
"\n"
"async def gen():\n"
" yield 1\n"
" yield 2\n"
"\n"
"async def func():\n"
" async with contextlib.aclosing(gen()) as g:\n"
" async for x in g:\n"
" break # Don't iterate until the end\n"
"\n"
"asyncio.run(func())"
msgstr ""
msgid ""
"As noted above, the cleanup code for these asynchronous generators is "
"deferred. The following example demonstrates that the finalization of an "
"asynchronous generator can occur in an unexpected order::"
msgstr ""
msgid ""
"import asyncio\n"
"work_done = False\n"
"\n"
"async def cursor():\n"
" try:\n"
" yield 1\n"
" finally:\n"
" assert work_done\n"
"\n"
"async def rows():\n"
" global work_done\n"
" try:\n"
" yield 2\n"
" finally:\n"
" await asyncio.sleep(0.1) # imitate some async work\n"
" work_done = True\n"
"\n"
"\n"
"async def main():\n"
" async for c in cursor():\n"
" async for r in rows():\n"
" break\n"
" break\n"
"\n"
"asyncio.run(main())"
msgstr ""
msgid "For this example, we get the following output::"
msgstr ""
msgid ""
"unhandled exception during asyncio.run() shutdown\n"
"task: <Task finished name='Task-3' coro=<<async_generator_athrow without "
"__name__>()> exception=AssertionError()>\n"
"Traceback (most recent call last):\n"
" File \"example.py\", line 6, in cursor\n"
" yield 1\n"
"asyncio.exceptions.CancelledError\n"
"\n"
"During handling of the above exception, another exception occurred:\n"
"\n"
"Traceback (most recent call last):\n"
" File \"example.py\", line 8, in cursor\n"
" assert work_done\n"
" ^^^^^^^^^\n"
"AssertionError"
msgstr ""
msgid ""
"The ``cursor()`` asynchronous generator was finalized before the ``rows`` "
"generator - an unexpected behavior."
msgstr ""
msgid ""
"The example can be fixed by explicitly closing the ``cursor`` and ``rows`` "
"async-generators::"
msgstr ""
msgid ""
"async def main():\n"
" async with contextlib.aclosing(cursor()) as cursor_gen:\n"
" async for c in cursor_gen:\n"
" async with contextlib.aclosing(rows()) as rows_gen:\n"
" async for r in rows_gen:\n"
" break\n"
" break"
msgstr ""
msgid "Create asynchronous generators only when the event loop is running"
msgstr ""
msgid ""
"It is recommended to create :term:`asynchronous generators <asynchronous "
"generator iterator>` only after the event loop has been created."
msgstr ""
msgid ""
"To ensure that asynchronous generators close reliably, the event loop uses "
"the :func:`sys.set_asyncgen_hooks` function to register callback functions. "
"These callbacks update the list of running asynchronous generators to keep "
"it in a consistent state."
msgstr ""
msgid ""
"When the :meth:`loop.shutdown_asyncgens() <asyncio.loop.shutdown_asyncgens>` "
"function is called, the running generators are stopped gracefully and the "
"list is cleared."
msgstr ""
msgid ""
"The asynchronous generator invokes the corresponding system hook during its "
"first iteration. At the same time, the generator records that the hook has "
"been called and does not call it again."
msgstr ""
msgid ""
"Therefore, if iteration begins before the event loop is created, the event "
"loop will not be able to add the generator to its list of active generators "
"because the hooks are set after the generator attempts to call them. "
"Consequently, the event loop will not be able to terminate the generator if "
"necessary."
msgstr ""
msgid "Consider the following example::"
msgstr ""
msgid ""
"import asyncio\n"
"\n"
"async def agenfn():\n"
" try:\n"
" yield 10\n"
" finally:\n"
" await asyncio.sleep(0)\n"
"\n"
"\n"
"with asyncio.Runner() as runner:\n"
" agen = agenfn()\n"
" print(runner.run(anext(agen)))\n"
" del agen"
msgstr ""
msgid ""
"10\n"
"Exception ignored while closing generator <async_generator object agenfn at "
"0x000002F71CD10D70>:\n"
"Traceback (most recent call last):\n"
" File \"example.py\", line 13, in <module>\n"
" del agen\n"
" ^^^^\n"
"RuntimeError: async generator ignored GeneratorExit"
msgstr ""
msgid "This example can be fixed as follows::"
msgstr ""
msgid ""
"import asyncio\n"
"\n"
"async def agenfn():\n"
" try:\n"
" yield 10\n"
" finally:\n"
" await asyncio.sleep(0)\n"
"\n"
"async def main():\n"
" agen = agenfn()\n"
" print(await anext(agen))\n"
" del agen\n"
"\n"
"asyncio.run(main())"
msgstr ""
msgid "Avoid concurrent iteration and closure of the same generator"
msgstr ""
msgid ""
"Async generators may be reentered while another :meth:`~agen.__anext__` / :"
"meth:`~agen.athrow` / :meth:`~agen.aclose` call is in progress. This may "
"lead to an inconsistent state of the async generator and can cause errors."
msgstr ""
msgid "Let's consider the following example::"
msgstr ""
msgid ""
"import asyncio\n"
"\n"
"async def consumer():\n"
" for idx in range(100):\n"
" await asyncio.sleep(0)\n"
" message = yield idx\n"
" print('received', message)\n"
"\n"
"async def amain():\n"
" agenerator = consumer()\n"
" await agenerator.asend(None)\n"
"\n"
" fa = asyncio.create_task(agenerator.asend('A'))\n"
" fb = asyncio.create_task(agenerator.asend('B'))\n"
" await fa\n"
" await fb\n"
"\n"
"asyncio.run(amain())"
msgstr ""
msgid ""
"received A\n"
"Traceback (most recent call last):\n"
" File \"test.py\", line 38, in <module>\n"
" asyncio.run(amain())\n"
" ~~~~~~~~~~~^^^^^^^^^\n"
" File \"Lib/asyncio/runners.py\", line 204, in run\n"
" return runner.run(main)\n"
" ~~~~~~~~~~^^^^^^\n"
" File \"Lib/asyncio/runners.py\", line 127, in run\n"
" return self._loop.run_until_complete(task)\n"
" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^\n"
" File \"Lib/asyncio/base_events.py\", line 719, in run_until_complete\n"
" return future.result()\n"
" ~~~~~~~~~~~~~^^\n"
" File \"test.py\", line 36, in amain\n"
" await fb\n"
"RuntimeError: anext(): asynchronous generator is already running"
msgstr ""
msgid ""
"Therefore, it is recommended to avoid using asynchronous generators in "
"parallel tasks or across multiple event loops."
msgstr ""