Repository navigation
Expand file tree
/
Copy pathexecutionmodel.po
More file actions
795 lines (650 loc) · 26.2 KB
/
Copy pathexecutionmodel.po
File metadata and controls
795 lines (650 loc) · 26.2 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
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
# 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-11-03 20:20+0000\n"
"PO-Revision-Date: 2025-09-16 00:02+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 "Execution model"
msgstr ""
msgid "Structure of a program"
msgstr ""
msgid ""
"A Python program is constructed from code blocks. A :dfn:`block` is a piece "
"of Python program text that is executed as a unit. The following are blocks: "
"a module, a function body, and a class definition. Each command typed "
"interactively is a block. A script file (a file given as standard input to "
"the interpreter or specified as a command line argument to the interpreter) "
"is a code block. A script command (a command specified on the interpreter "
"command line with the :option:`-c` option) is a code block. A module run as "
"a top level script (as module ``__main__``) from the command line using "
"a :option:`-m` argument is also a code block. The string argument passed to "
"the built-in functions :func:`eval` and :func:`exec` is a code block."
msgstr ""
msgid ""
"A code block is executed in an :dfn:`execution frame`. A frame contains "
"some administrative information (used for debugging) and determines where "
"and how execution continues after the code block's execution has completed."
msgstr ""
msgid "Naming and binding"
msgstr ""
msgid "Binding of names"
msgstr ""
msgid ""
":dfn:`Names` refer to objects. Names are introduced by name binding "
"operations."
msgstr ""
msgid "The following constructs bind names:"
msgstr ""
msgid "formal parameters to functions,"
msgstr ""
msgid "class definitions,"
msgstr ""
msgid "function definitions,"
msgstr ""
msgid "assignment expressions,"
msgstr ""
msgid ""
":ref:`targets <assignment>` that are identifiers if occurring in an "
"assignment:"
msgstr ""
msgid ":keyword:`for` loop header,"
msgstr ""
msgid ""
"after :keyword:`!as` in a :keyword:`with` statement, :keyword:`except` "
"clause, :keyword:`except* <except_star>` clause, or in the as-pattern in "
"structural pattern matching,"
msgstr ""
msgid "in a capture pattern in structural pattern matching"
msgstr ""
msgid ":keyword:`import` statements."
msgstr ""
msgid ":keyword:`type` statements."
msgstr ""
msgid ":ref:`type parameter lists <type-params>`."
msgstr ""
msgid ""
"The :keyword:`!import` statement of the form ``from ... import *`` binds all "
"names defined in the imported module, except those beginning with an "
"underscore. This form may only be used at the module level."
msgstr ""
msgid ""
"A target occurring in a :keyword:`del` statement is also considered bound "
"for this purpose (though the actual semantics are to unbind the name)."
msgstr ""
msgid ""
"Each assignment or import statement occurs within a block defined by a class "
"or function definition or at the module level (the top-level code block)."
msgstr ""
msgid ""
"If a name is bound in a block, it is a local variable of that block, unless "
"declared as :keyword:`nonlocal` or :keyword:`global`. If a name is bound at "
"the module level, it is a global variable. (The variables of the module "
"code block are local and global.) If a variable is used in a code block but "
"not defined there, it is a :term:`free variable`."
msgstr ""
msgid ""
"Each occurrence of a name in the program text refers to the :dfn:`binding` "
"of that name established by the following name resolution rules."
msgstr ""
msgid "Resolution of names"
msgstr ""
msgid ""
"A :dfn:`scope` defines the visibility of a name within a block. If a local "
"variable is defined in a block, its scope includes that block. If the "
"definition occurs in a function block, the scope extends to any blocks "
"contained within the defining one, unless a contained block introduces a "
"different binding for the name."
msgstr ""
msgid ""
"When a name is used in a code block, it is resolved using the nearest "
"enclosing scope. The set of all such scopes visible to a code block is "
"called the block's :dfn:`environment`."
msgstr ""
msgid ""
"When a name is not found at all, a :exc:`NameError` exception is raised. If "
"the current scope is a function scope, and the name refers to a local "
"variable that has not yet been bound to a value at the point where the name "
"is used, an :exc:`UnboundLocalError` exception is "
"raised. :exc:`UnboundLocalError` is a subclass of :exc:`NameError`."
msgstr ""
msgid ""
"If a name binding operation occurs anywhere within a code block, all uses of "
"the name within the block are treated as references to the current block. "
"This can lead to errors when a name is used within a block before it is "
"bound. This rule is subtle. Python lacks declarations and allows name "
"binding operations to occur anywhere within a code block. The local "
"variables of a code block can be determined by scanning the entire text of "
"the block for name binding operations. See :ref:`the FAQ entry on "
"UnboundLocalError <faq-unboundlocalerror>` for examples."
msgstr ""
msgid ""
"If the :keyword:`global` statement occurs within a block, all uses of the "
"names specified in the statement refer to the bindings of those names in the "
"top-level namespace. Names are resolved in the top-level namespace by "
"searching the global namespace, i.e. the namespace of the module containing "
"the code block, and the builtins namespace, the namespace of the "
"module :mod:`builtins`. The global namespace is searched first. If the "
"names are not found there, the builtins namespace is searched next. If the "
"names are also not found in the builtins namespace, new variables are "
"created in the global namespace. The global statement must precede all uses "
"of the listed names."
msgstr ""
msgid ""
"The :keyword:`global` statement has the same scope as a name binding "
"operation in the same block. If the nearest enclosing scope for a free "
"variable contains a global statement, the free variable is treated as a "
"global."
msgstr ""
msgid ""
"The :keyword:`nonlocal` statement causes corresponding names to refer to "
"previously bound variables in the nearest enclosing function "
"scope. :exc:`SyntaxError` is raised at compile time if the given name does "
"not exist in any enclosing function scope. :ref:`Type parameters <type-"
"params>` cannot be rebound with the :keyword:`!nonlocal` statement."
msgstr ""
msgid ""
"The namespace for a module is automatically created the first time a module "
"is imported. The main module for a script is always called :mod:`__main__`."
msgstr ""
msgid ""
"Class definition blocks and arguments to :func:`exec` and :func:`eval` are "
"special in the context of name resolution. A class definition is an "
"executable statement that may use and define names. These references follow "
"the normal rules for name resolution with an exception that unbound local "
"variables are looked up in the global namespace. The namespace of the class "
"definition becomes the attribute dictionary of the class. The scope of names "
"defined in a class block is limited to the class block; it does not extend "
"to the code blocks of methods. This includes comprehensions and generator "
"expressions, but it does not include :ref:`annotation scopes <annotation-"
"scopes>`, which have access to their enclosing class scopes. This means that "
"the following will fail::"
msgstr ""
msgid ""
"class A:\n"
" a = 42\n"
" b = list(a + i for i in range(10))"
msgstr ""
msgid "However, the following will succeed::"
msgstr ""
msgid ""
"class A:\n"
" type Alias = Nested\n"
" class Nested: pass\n"
"\n"
"print(A.Alias.__value__) # <type 'A.Nested'>"
msgstr ""
msgid "Annotation scopes"
msgstr ""
msgid ""
":term:`Annotations <annotation>`, :ref:`type parameter lists <type-params>` "
"and :keyword:`type` statements introduce *annotation scopes*, which behave "
"mostly like function scopes, but with some exceptions discussed below."
msgstr ""
msgid "Annotation scopes are used in the following contexts:"
msgstr ""
msgid ":term:`Function annotations <function annotation>`."
msgstr ""
msgid ":term:`Variable annotations <variable annotation>`."
msgstr ""
msgid ""
"Type parameter lists for :ref:`generic type aliases <generic-type-aliases>`."
msgstr ""
msgid ""
"Type parameter lists for :ref:`generic functions <generic-functions>`. A "
"generic function's annotations are executed within the annotation scope, but "
"its defaults and decorators are not."
msgstr ""
msgid ""
"Type parameter lists for :ref:`generic classes <generic-classes>`. A generic "
"class's base classes and keyword arguments are executed within the "
"annotation scope, but its decorators are not."
msgstr ""
msgid ""
"The bounds, constraints, and default values for type parameters "
"(:ref:`lazily evaluated <lazy-evaluation>`)."
msgstr ""
msgid "The value of type aliases (:ref:`lazily evaluated <lazy-evaluation>`)."
msgstr ""
msgid "Annotation scopes differ from function scopes in the following ways:"
msgstr ""
msgid ""
"Annotation scopes have access to their enclosing class namespace. If an "
"annotation scope is immediately within a class scope, or within another "
"annotation scope that is immediately within a class scope, the code in the "
"annotation scope can use names defined in the class scope as if it were "
"executed directly within the class body. This contrasts with regular "
"functions defined within classes, which cannot access names defined in the "
"class scope."
msgstr ""
msgid ""
"Expressions in annotation scopes cannot contain :keyword:`yield`, ``yield "
"from``, :keyword:`await`, or :token:`:= <python-"
"grammar:assignment_expression>` expressions. (These expressions are allowed "
"in other scopes contained within the annotation scope.)"
msgstr ""
msgid ""
"Names defined in annotation scopes cannot be rebound "
"with :keyword:`nonlocal` statements in inner scopes. This includes only type "
"parameters, as no other syntactic elements that can appear within annotation "
"scopes can introduce new names."
msgstr ""
msgid ""
"While annotation scopes have an internal name, that name is not reflected in "
"the :term:`qualified name` of objects defined within the scope. Instead, "
"the :attr:`~definition.__qualname__` of such objects is as if the object "
"were defined in the enclosing scope."
msgstr ""
msgid "Annotation scopes were introduced in Python 3.12 as part of :pep:`695`."
msgstr ""
msgid ""
"Annotation scopes are also used for type parameter defaults, as introduced "
"by :pep:`696`."
msgstr ""
msgid ""
"Annotation scopes are now also used for annotations, as specified "
"in :pep:`649` and :pep:`749`."
msgstr ""
msgid "Lazy evaluation"
msgstr ""
msgid ""
"Most annotation scopes are *lazily evaluated*. This includes annotations, "
"the values of type aliases created through the :keyword:`type` statement, "
"and the bounds, constraints, and default values of type variables created "
"through the :ref:`type parameter syntax <type-params>`. This means that they "
"are not evaluated when the type alias or type variable is created, or when "
"the object carrying annotations is created. Instead, they are only evaluated "
"when necessary, for example when the ``__value__`` attribute on a type alias "
"is accessed."
msgstr ""
msgid "Example:"
msgstr ""
msgid ""
">>> type Alias = 1/0\n"
">>> Alias.__value__\n"
"Traceback (most recent call last):\n"
" ...\n"
"ZeroDivisionError: division by zero\n"
">>> def func[T: 1/0](): pass\n"
">>> T = func.__type_params__[0]\n"
">>> T.__bound__\n"
"Traceback (most recent call last):\n"
" ...\n"
"ZeroDivisionError: division by zero"
msgstr ""
msgid ""
"Here the exception is raised only when the ``__value__`` attribute of the "
"type alias or the ``__bound__`` attribute of the type variable is accessed."
msgstr ""
msgid ""
"This behavior is primarily useful for references to types that have not yet "
"been defined when the type alias or type variable is created. For example, "
"lazy evaluation enables creation of mutually recursive type aliases::"
msgstr ""
msgid ""
"from typing import Literal\n"
"\n"
"type SimpleExpr = int | Parenthesized\n"
"type Parenthesized = tuple[Literal[\"(\"], Expr, Literal[\")\"]]\n"
"type Expr = SimpleExpr | tuple[SimpleExpr, Literal[\"+\", \"-\"], Expr]"
msgstr ""
msgid ""
"Lazily evaluated values are evaluated in :ref:`annotation scope <annotation-"
"scopes>`, which means that names that appear inside the lazily evaluated "
"value are looked up as if they were used in the immediately enclosing scope."
msgstr ""
msgid "Builtins and restricted execution"
msgstr ""
msgid ""
"Users should not touch ``__builtins__``; it is strictly an implementation "
"detail. Users wanting to override values in the builtins namespace "
"should :keyword:`import` the :mod:`builtins` module and modify its "
"attributes appropriately."
msgstr ""
msgid ""
"The builtins namespace associated with the execution of a code block is "
"actually found by looking up the name ``__builtins__`` in its global "
"namespace; this should be a dictionary or a module (in the latter case the "
"module's dictionary is used). By default, when in the :mod:`__main__` "
"module, ``__builtins__`` is the built-in module :mod:`builtins`; when in any "
"other module, ``__builtins__`` is an alias for the dictionary of "
"the :mod:`builtins` module itself."
msgstr ""
msgid "Interaction with dynamic features"
msgstr ""
msgid ""
"Name resolution of free variables occurs at runtime, not at compile time. "
"This means that the following code will print 42::"
msgstr ""
msgid ""
"i = 10\n"
"def f():\n"
" print(i)\n"
"i = 42\n"
"f()"
msgstr ""
msgid ""
"The :func:`eval` and :func:`exec` functions do not have access to the full "
"environment for resolving names. Names may be resolved in the local and "
"global namespaces of the caller. Free variables are not resolved in the "
"nearest enclosing namespace, but in the global namespace. [#]_ "
"The :func:`exec` and :func:`eval` functions have optional arguments to "
"override the global and local namespace. If only one namespace is "
"specified, it is used for both."
msgstr ""
msgid "Exceptions"
msgstr ""
msgid ""
"Exceptions are a means of breaking out of the normal flow of control of a "
"code block in order to handle errors or other exceptional conditions. An "
"exception is *raised* at the point where the error is detected; it may be "
"*handled* by the surrounding code block or by any code block that directly "
"or indirectly invoked the code block where the error occurred."
msgstr ""
msgid ""
"The Python interpreter raises an exception when it detects a run-time error "
"(such as division by zero). A Python program can also explicitly raise an "
"exception with the :keyword:`raise` statement. Exception handlers are "
"specified with the :keyword:`try` ... :keyword:`except` statement. "
"The :keyword:`finally` clause of such a statement can be used to specify "
"cleanup code which does not handle the exception, but is executed whether an "
"exception occurred or not in the preceding code."
msgstr ""
msgid ""
"Python uses the \"termination\" model of error handling: an exception "
"handler can find out what happened and continue execution at an outer level, "
"but it cannot repair the cause of the error and retry the failing operation "
"(except by re-entering the offending piece of code from the top)."
msgstr ""
msgid ""
"When an exception is not handled at all, the interpreter terminates "
"execution of the program, or returns to its interactive main loop. In "
"either case, it prints a stack traceback, except when the exception "
"is :exc:`SystemExit`."
msgstr ""
msgid ""
"Exceptions are identified by class instances. The :keyword:`except` clause "
"is selected depending on the class of the instance: it must reference the "
"class of the instance or a :term:`non-virtual base class <abstract base "
"class>` thereof. The instance can be received by the handler and can carry "
"additional information about the exceptional condition."
msgstr ""
msgid ""
"Exception messages are not part of the Python API. Their contents may "
"change from one version of Python to the next without warning and should not "
"be relied on by code which will run under multiple versions of the "
"interpreter."
msgstr ""
msgid ""
"See also the description of the :keyword:`try` statement in "
"section :ref:`try` and :keyword:`raise` statement in section :ref:`raise`."
msgstr ""
msgid "Runtime Components"
msgstr ""
msgid "General Computing Model"
msgstr ""
msgid ""
"Python's execution model does not operate in a vacuum. It runs on a host "
"machine and through that host's runtime environment, including its operating "
"system (OS), if there is one. When a program runs, the conceptual layers of "
"how it runs on the host look something like this:"
msgstr ""
msgid "**host machine**"
msgstr ""
msgid "**process** (global resources)"
msgstr ""
msgid "**thread** (runs machine code)"
msgstr ""
msgid ""
"Each process represents a program running on the host. Think of each "
"process itself as the data part of its program. Think of the process' "
"threads as the execution part of the program. This distinction will be "
"important to understand the conceptual Python runtime."
msgstr ""
msgid ""
"The process, as the data part, is the execution context in which the program "
"runs. It mostly consists of the set of resources assigned to the program by "
"the host, including memory, signals, file handles, sockets, and environment "
"variables."
msgstr ""
msgid ""
"Processes are isolated and independent from one another. (The same is true "
"for hosts.) The host manages the process' access to its assigned resources, "
"in addition to coordinating between processes."
msgstr ""
msgid ""
"Each thread represents the actual execution of the program's machine code, "
"running relative to the resources assigned to the program's process. It's "
"strictly up to the host how and when that execution takes place."
msgstr ""
msgid ""
"From the point of view of Python, a program always starts with exactly one "
"thread. However, the program may grow to run in multiple simultaneous "
"threads. Not all hosts support multiple threads per process, but most do. "
"Unlike processes, threads in a process are not isolated and independent from "
"one another. Specifically, all threads in a process share all of the "
"process' resources."
msgstr ""
msgid ""
"The fundamental point of threads is that each one does *run* independently, "
"at the same time as the others. That may be only conceptually at the same "
"time (\"concurrently\") or physically (\"in parallel\"). Either way, the "
"threads effectively run at a non-synchronized rate."
msgstr ""
msgid ""
"That non-synchronized rate means none of the process' memory is guaranteed "
"to stay consistent for the code running in any given thread. Thus multi-"
"threaded programs must take care to coordinate access to intentionally "
"shared resources. Likewise, they must take care to be absolutely diligent "
"about not accessing any *other* resources in multiple threads; otherwise two "
"threads running at the same time might accidentally interfere with each "
"other's use of some shared data. All this is true for both Python programs "
"and the Python runtime."
msgstr ""
msgid ""
"The cost of this broad, unstructured requirement is the tradeoff for the "
"kind of raw concurrency that threads provide. The alternative to the "
"required discipline generally means dealing with non-deterministic bugs and "
"data corruption."
msgstr ""
msgid "Python Runtime Model"
msgstr ""
msgid ""
"The same conceptual layers apply to each Python program, with some extra "
"data layers specific to Python:"
msgstr ""
msgid "Python global runtime (*state*)"
msgstr ""
msgid "Python interpreter (*state*)"
msgstr ""
msgid "**thread** (runs Python bytecode and \"C-API\")"
msgstr ""
msgid "Python thread *state*"
msgstr ""
msgid ""
"At the conceptual level: when a Python program starts, it looks exactly like "
"that diagram, with one of each. The runtime may grow to include multiple "
"interpreters, and each interpreter may grow to include multiple thread "
"states."
msgstr ""
msgid ""
"A Python implementation won't necessarily implement the runtime layers "
"distinctly or even concretely. The only exception is places where distinct "
"layers are directly specified or exposed to users, like through "
"the :mod:`threading` module."
msgstr ""
msgid ""
"The initial interpreter is typically called the \"main\" interpreter. Some "
"Python implementations, like CPython, assign special roles to the main "
"interpreter."
msgstr ""
msgid ""
"Likewise, the host thread where the runtime was initialized is known as the "
"\"main\" thread. It may be different from the process' initial thread, "
"though they are often the same. In some cases \"main thread\" may be even "
"more specific and refer to the initial thread state. A Python runtime might "
"assign specific responsibilities to the main thread, such as handling "
"signals."
msgstr ""
msgid ""
"As a whole, the Python runtime consists of the global runtime state, "
"interpreters, and thread states. The runtime ensures all that state stays "
"consistent over its lifetime, particularly when used with multiple host "
"threads."
msgstr ""
msgid ""
"The global runtime, at the conceptual level, is just a set of interpreters. "
"While those interpreters are otherwise isolated and independent from one "
"another, they may share some data or other resources. The runtime is "
"responsible for managing these global resources safely. The actual nature "
"and management of these resources is implementation-specific. Ultimately, "
"the external utility of the global runtime is limited to managing "
"interpreters."
msgstr ""
msgid ""
"In contrast, an \"interpreter\" is conceptually what we would normally think "
"of as the (full-featured) \"Python runtime\". When machine code executing "
"in a host thread interacts with the Python runtime, it calls into Python in "
"the context of a specific interpreter."
msgstr ""
msgid ""
"The term \"interpreter\" here is not the same as the \"bytecode "
"interpreter\", which is what regularly runs in threads, executing compiled "
"Python code."
msgstr ""
msgid ""
"In an ideal world, \"Python runtime\" would refer to what we currently call "
"\"interpreter\". However, it's been called \"interpreter\" at least since "
"introduced in 1997 (`CPython:a027efa5b`_)."
msgstr ""
msgid ""
"Each interpreter completely encapsulates all of the non-process-global, non-"
"thread-specific state needed for the Python runtime to work. Notably, the "
"interpreter's state persists between uses. It includes fundamental data "
"like :data:`sys.modules`. The runtime ensures multiple threads using the "
"same interpreter will safely share it between them."
msgstr ""
msgid ""
"A Python implementation may support using multiple interpreters at the same "
"time in the same process. They are independent and isolated from one "
"another. For example, each interpreter has its own :data:`sys.modules`."
msgstr ""
msgid ""
"For thread-specific runtime state, each interpreter has a set of thread "
"states, which it manages, in the same way the global runtime contains a set "
"of interpreters. It can have thread states for as many host threads as it "
"needs. It may even have multiple thread states for the same host thread, "
"though that isn't as common."
msgstr ""
msgid ""
"Each thread state, conceptually, has all the thread-specific runtime data an "
"interpreter needs to operate in one host thread. The thread state includes "
"the current raised exception and the thread's Python call stack. It may "
"include other thread-specific resources."
msgstr ""
msgid ""
"The term \"Python thread\" can sometimes refer to a thread state, but "
"normally it means a thread created using the :mod:`threading` module."
msgstr ""
msgid ""
"Each thread state, over its lifetime, is always tied to exactly one "
"interpreter and exactly one host thread. It will only ever be used in that "
"thread and with that interpreter."
msgstr ""
msgid ""
"Multiple thread states may be tied to the same host thread, whether for "
"different interpreters or even the same interpreter. However, for any given "
"host thread, only one of the thread states tied to it can be used by the "
"thread at a time."
msgstr ""
msgid ""
"Thread states are isolated and independent from one another and don't share "
"any data, except for possibly sharing an interpreter and objects or other "
"resources belonging to that interpreter."
msgstr ""
msgid ""
"Once a program is running, new Python threads can be created using "
"the :mod:`threading` module (on platforms and Python implementations that "
"support threads). Additional processes can be created using "
"the :mod:`os`, :mod:`subprocess`, and :mod:`multiprocessing` modules. "
"Interpreters can be created and used with "
"the :mod:`~concurrent.interpreters` module. Coroutines (async) can be run "
"using :mod:`asyncio` in each interpreter, typically only in a single thread "
"(often the main thread)."
msgstr ""
msgid "Footnotes"
msgstr ""
msgid ""
"This limitation occurs because the code that is executed by these operations "
"is not available at the time the module is compiled."
msgstr ""
msgid "execution model"
msgstr ""
msgid "code"
msgstr ""
msgid "block"
msgstr ""
msgid "execution"
msgstr ""
msgid "frame"
msgstr ""
msgid "namespace"
msgstr ""
msgid "scope"
msgstr ""
msgid "name"
msgstr ""
msgid "binding"
msgstr ""
msgid "from"
msgstr ""
msgid "import statement"
msgstr ""
msgid "free"
msgstr ""
msgid "variable"
msgstr ""
msgid "environment"
msgstr ""
msgid "NameError (built-in exception)"
msgstr ""
msgid "UnboundLocalError"
msgstr ""
msgid "module"
msgstr ""
msgid "__main__"
msgstr ""
msgid "restricted"
msgstr ""
msgid "exception"
msgstr ""
msgid "raise an exception"
msgstr ""
msgid "handle an exception"
msgstr ""
msgid "exception handler"
msgstr ""
msgid "errors"
msgstr ""
msgid "error handling"
msgstr ""
msgid "termination model"
msgstr ""
msgid "SystemExit (built-in exception)"
msgstr ""