-
Notifications
You must be signed in to change notification settings - Fork 10
Expand file tree
/
Copy pathdatamodel.po
More file actions
2921 lines (2008 loc) · 146 KB
/
Copy pathdatamodel.po
File metadata and controls
2921 lines (2008 loc) · 146 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
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# 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:
# Alireza Shabani (Revisto) <theRevisto@gmail.com>, 2025
# Danial Behzadi <dani.behzi@ubuntu.com>, 2025
# Rafael Fontenelle <rffontenelle@gmail.com>, 2025
# Sepehr Rasouli <sepehrrasouli06@gmail.com>, 2026
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.14\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-08-18 04:30+0000\n"
"PO-Revision-Date: 2021-06-28 01:19+0000\n"
"Last-Translator: Sepehr Rasouli <sepehrrasouli06@gmail.com>, 2026\n"
"Language-Team: Persian (https://github.com/revisto/python-docs-fa/fa/)\n"
"Language: fa\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"
msgid "Data model"
msgstr ""
msgid "Objects, values and types"
msgstr ""
msgid ":dfn:`Objects` are Python's abstraction for data. All data in a Python program is represented by objects or by relations between objects. Even code is represented by objects."
msgstr ""
msgid "Every object has an identity, a type and a value. An object's *identity* never changes once it has been created; you may think of it as the object's address in memory. The :keyword:`is` operator compares the identity of two objects; the :func:`id` function returns an integer representing its identity."
msgstr ""
msgid "For CPython, ``id(x)`` is the memory address where ``x`` is stored."
msgstr ""
msgid "An object's type determines the operations that the object supports (e.g., \"does it have a length?\") and also defines the possible values for objects of that type. The :func:`type` function returns an object's type (which is an object itself). Like its identity, an object's :dfn:`type` is also unchangeable. [#]_"
msgstr ""
msgid "The *value* of some objects can change. Objects whose value can change are said to be *mutable*; objects whose value is unchangeable once they are created are called *immutable*. (The value of an immutable container object that contains a reference to a mutable object can change when the latter's value is changed; however the container is still considered immutable, because the collection of objects it contains cannot be changed. So, immutability is not strictly the same as having an unchangeable value, it is more subtle.) An object's mutability is determined by its type; for instance, numbers, strings and tuples are immutable, while dictionaries and lists are mutable."
msgstr ""
msgid "Objects are never explicitly destroyed; however, when they become unreachable they may be garbage-collected. An implementation is allowed to postpone garbage collection or omit it altogether --- it is a matter of implementation quality how garbage collection is implemented, as long as no objects are collected that are still reachable."
msgstr ""
msgid "CPython currently uses a reference-counting scheme with (optional) delayed detection of cyclically linked garbage, which collects most objects as soon as they become unreachable, but is not guaranteed to collect garbage containing circular references. See the documentation of the :mod:`gc` module for information on controlling the collection of cyclic garbage. Other implementations act differently and CPython may change. Do not depend on immediate finalization of objects when they become unreachable (so you should always close files explicitly)."
msgstr ""
msgid "Note that the use of the implementation's tracing or debugging facilities may keep objects alive that would normally be collectable. Also note that catching an exception with a :keyword:`try`...\\ :keyword:`except` statement may keep objects alive."
msgstr ""
msgid "Some objects contain references to \"external\" resources such as open files or windows. It is understood that these resources are freed when the object is garbage-collected, but since garbage collection is not guaranteed to happen, such objects also provide an explicit way to release the external resource, usually a :meth:`!close` method. Programs are strongly recommended to explicitly close such objects. The :keyword:`try`...\\ :keyword:`finally` statement and the :keyword:`with` statement provide convenient ways to do this."
msgstr ""
msgid "Some objects contain references to other objects; these are called *containers*. Examples of containers are tuples, lists and dictionaries. The references are part of a container's value. In most cases, when we talk about the value of a container, we imply the values, not the identities of the contained objects; however, when we talk about the mutability of a container, only the identities of the immediately contained objects are implied. So, if an immutable container (like a tuple) contains a reference to a mutable object, its value changes if that mutable object is changed."
msgstr ""
msgid "Types affect almost all aspects of object behavior. Even the importance of object identity is affected in some sense: for immutable types, operations that compute new values may actually return a reference to any existing object with the same type and value, while for mutable objects this is not allowed. For example, after ``a = 1; b = 1``, *a* and *b* may or may not refer to the same object with the value one, depending on the implementation. This is because :class:`int` is an immutable type, so the reference to ``1`` can be reused. This behaviour depends on the implementation used, so should not be relied upon, but is something to be aware of when making use of object identity tests. However, after ``c = []; d = []``, *c* and *d* are guaranteed to refer to two different, unique, newly created empty lists. (Note that ``e = f = []`` assigns the *same* object to both *e* and *f*.)"
msgstr ""
msgid "The standard type hierarchy"
msgstr ""
msgid "Below is a list of the types that are built into Python. Extension modules (written in C, Java, or other languages, depending on the implementation) can define additional types. Future versions of Python may add types to the type hierarchy (e.g., rational numbers, efficiently stored arrays of integers, etc.), although such additions will often be provided via the standard library instead."
msgstr ""
msgid "Some of the type descriptions below contain a paragraph listing 'special attributes.' These are attributes that provide access to the implementation and are not intended for general use. Their definition may change in the future."
msgstr ""
msgid "None"
msgstr ""
msgid "This type has a single value. There is a single object with this value. This object is accessed through the built-in name ``None``. It is used to signify the absence of a value in many situations, e.g., it is returned from functions that don't explicitly return anything. Its truth value is false."
msgstr ""
msgid "NotImplemented"
msgstr ""
msgid "This type has a single value. There is a single object with this value. This object is accessed through the built-in name :data:`NotImplemented`. Numeric methods and rich comparison methods should return this value if they do not implement the operation for the operands provided. (The interpreter will then try the reflected operation, or some other fallback, depending on the operator.) It should not be evaluated in a boolean context."
msgstr ""
msgid "See :ref:`implementing-the-arithmetic-operations` for more details."
msgstr ""
msgid "Evaluating :data:`NotImplemented` in a boolean context was deprecated."
msgstr ""
msgid "Evaluating :data:`NotImplemented` in a boolean context now raises a :exc:`TypeError`. It previously evaluated to :const:`True` and emitted a :exc:`DeprecationWarning` since Python 3.9."
msgstr ""
msgid "Ellipsis"
msgstr ""
msgid "This type has a single value. There is a single object with this value. This object is accessed through the literal ``...`` or the built-in name ``Ellipsis``. Its truth value is true."
msgstr ""
msgid ":class:`numbers.Number`"
msgstr ""
msgid "These are created by numeric literals and returned as results by arithmetic operators and arithmetic built-in functions. Numeric objects are immutable; once created their value never changes. Python numbers are of course strongly related to mathematical numbers, but subject to the limitations of numerical representation in computers."
msgstr ""
msgid "The string representations of the numeric classes, computed by :meth:`~object.__repr__` and :meth:`~object.__str__`, have the following properties:"
msgstr ""
msgid "They are valid numeric literals which, when passed to their class constructor, produce an object having the value of the original numeric."
msgstr ""
msgid "The representation is in base 10, when possible."
msgstr ""
msgid "Leading zeros, possibly excepting a single zero before a decimal point, are not shown."
msgstr ""
msgid "Trailing zeros, possibly excepting a single zero after a decimal point, are not shown."
msgstr ""
msgid "A sign is shown only when the number is negative."
msgstr ""
msgid "Python distinguishes between integers, floating-point numbers, and complex numbers:"
msgstr ""
msgid ":class:`numbers.Integral`"
msgstr ""
msgid "These represent elements from the mathematical set of integers (positive and negative)."
msgstr ""
msgid "The rules for integer representation are intended to give the most meaningful interpretation of shift and mask operations involving negative integers."
msgstr ""
msgid "There are two types of integers:"
msgstr ""
msgid "Integers (:class:`int`)"
msgstr ""
msgid "These represent numbers in an unlimited range, subject to available (virtual) memory only. For the purpose of shift and mask operations, a binary representation is assumed, and negative numbers are represented in a variant of 2's complement which gives the illusion of an infinite string of sign bits extending to the left."
msgstr ""
msgid "Booleans (:class:`bool`)"
msgstr ""
msgid "These represent the truth values False and True. The two objects representing the values ``False`` and ``True`` are the only Boolean objects. The Boolean type is a subtype of the integer type, and Boolean values behave like the values 0 and 1, respectively, in almost all contexts, the exception being that when converted to a string, the strings ``\"False\"`` or ``\"True\"`` are returned, respectively."
msgstr ""
msgid ":class:`numbers.Real` (:class:`float`)"
msgstr ""
msgid "These represent machine-level double precision floating-point numbers. You are at the mercy of the underlying machine architecture (and C or Java implementation) for the accepted range and handling of overflow. Python does not support single-precision floating-point numbers; the savings in processor and memory usage that are usually the reason for using these are dwarfed by the overhead of using objects in Python, so there is no reason to complicate the language with two kinds of floating-point numbers."
msgstr ""
msgid ":class:`numbers.Complex` (:class:`complex`)"
msgstr ""
msgid "These represent complex numbers as a pair of machine-level double precision floating-point numbers. The same caveats apply as for floating-point numbers. The real and imaginary parts of a complex number ``z`` can be retrieved through the read-only attributes ``z.real`` and ``z.imag``."
msgstr ""
msgid "Sequences"
msgstr ""
msgid "These represent finite ordered sets indexed by non-negative numbers. The built-in function :func:`len` returns the number of items of a sequence. When the length of a sequence is *n*, the index set contains the numbers 0, 1, ..., *n*-1. Item *i* of sequence *a* is selected by ``a[i]``. Some sequences, including built-in sequences, interpret negative subscripts by adding the sequence length. For example, ``a[-2]`` equals ``a[n-2]``, the second to last item of sequence a with length ``n``."
msgstr ""
msgid "The resulting value must be a nonnegative integer less than the number of items in the sequence. If it is not, an :exc:`IndexError` is raised."
msgstr ""
msgid "Sequences also support slicing: ``a[start:stop]`` selects all items with index *k* such that *start* ``<=`` *k* ``<`` *stop*. When used as an expression, a slice is a sequence of the same type. The comment above about negative subscripts also applies to negative slice positions. Note that no error is raised if a slice position is less than zero or larger than the length of the sequence."
msgstr ""
msgid "If *start* is missing or :data:`None`, slicing behaves as if *start* was zero. If *stop* is missing or ``None``, slicing behaves as if *stop* was equal to the length of the sequence."
msgstr ""
msgid "Some sequences also support \"extended slicing\" with a third \"step\" parameter: ``a[i:j:k]`` selects all items of *a* with index *x* where ``x = i + n*k``, *n* ``>=`` ``0`` and *i* ``<=`` *x* ``<`` *j*."
msgstr ""
msgid "Sequences are distinguished according to their mutability:"
msgstr ""
msgid "Immutable sequences"
msgstr ""
msgid "An object of an immutable sequence type cannot change once it is created. (If the object contains references to other objects, these other objects may be mutable and may be changed; however, the collection of objects directly referenced by an immutable object cannot change.)"
msgstr ""
msgid "The following types are immutable sequences:"
msgstr ""
msgid "Strings"
msgstr ""
msgid "A string (:class:`str`) is a sequence of values that represent :dfn:`characters`, or more formally, *Unicode code points*. All the code points in the range ``0`` to ``0x10FFFF`` can be represented in a string."
msgstr ""
msgid "Python doesn't have a dedicated *character* type. Instead, every code point in the string is represented as a string object with length ``1``."
msgstr ""
msgid "The built-in function :func:`ord` converts a code point from its string form to an integer in the range ``0`` to ``0x10FFFF``; :func:`chr` converts an integer in the range ``0`` to ``0x10FFFF`` to the corresponding length ``1`` string object. :meth:`str.encode` can be used to convert a :class:`str` to :class:`bytes` using the given text encoding, and :meth:`bytes.decode` can be used to achieve the opposite."
msgstr ""
msgid "Tuples"
msgstr ""
msgid "The items of a :class:`tuple` are arbitrary Python objects. Tuples of two or more items are formed by comma-separated lists of expressions. A tuple of one item (a 'singleton') can be formed by affixing a comma to an expression (an expression by itself does not create a tuple, since parentheses must be usable for grouping of expressions). An empty tuple can be formed by an empty pair of parentheses."
msgstr ""
msgid "Bytes"
msgstr ""
msgid "A :class:`bytes` object is an immutable array. The items are 8-bit bytes, represented by integers in the range 0 <= x < 256. Bytes literals (like ``b'abc'``) and the built-in :func:`bytes` constructor can be used to create bytes objects. Also, bytes objects can be decoded to strings via the :meth:`~bytes.decode` method."
msgstr ""
msgid "Mutable sequences"
msgstr ""
msgid "Mutable sequences can be changed after they are created. The subscription and slicing notations can be used as the target of assignment and :keyword:`del` (delete) statements."
msgstr ""
msgid "The :mod:`collections` and :mod:`array` module provide additional examples of mutable sequence types."
msgstr ""
msgid "There are currently two intrinsic mutable sequence types:"
msgstr ""
msgid "Lists"
msgstr ""
msgid "The items of a list are arbitrary Python objects. Lists are formed by placing a comma-separated list of expressions in square brackets. (Note that there are no special cases needed to form lists of length 0 or 1.)"
msgstr ""
msgid "Byte Arrays"
msgstr ""
msgid "A bytearray object is a mutable array. They are created by the built-in :func:`bytearray` constructor. Aside from being mutable (and hence unhashable), byte arrays otherwise provide the same interface and functionality as immutable :class:`bytes` objects."
msgstr ""
msgid "Set types"
msgstr ""
msgid "These represent unordered, finite sets of unique, immutable objects. As such, they cannot be indexed by any subscript. However, they can be iterated over, and the built-in function :func:`len` returns the number of items in a set. Common uses for sets are fast membership testing, removing duplicates from a sequence, and computing mathematical operations such as intersection, union, difference, and symmetric difference."
msgstr ""
msgid "For set elements, the same immutability rules apply as for dictionary keys. Note that numeric types obey the normal rules for numeric comparison: if two numbers compare equal (e.g., ``1`` and ``1.0``), only one of them can be contained in a set."
msgstr ""
msgid "There are currently two intrinsic set types:"
msgstr ""
msgid "Sets"
msgstr ""
msgid "These represent a mutable set. They are created by the built-in :func:`set` constructor and can be modified afterwards by several methods, such as :meth:`~set.add`."
msgstr ""
msgid "Frozen sets"
msgstr ""
msgid "These represent an immutable set. They are created by the built-in :func:`frozenset` constructor. As a frozenset is immutable and :term:`hashable`, it can be used again as an element of another set, or as a dictionary key."
msgstr ""
msgid "Mappings"
msgstr ""
msgid "These represent finite sets of objects indexed by arbitrary index sets. The subscript notation ``a[k]`` selects the item indexed by ``k`` from the mapping ``a``; this can be used in expressions and as the target of assignments or :keyword:`del` statements. The built-in function :func:`len` returns the number of items in a mapping."
msgstr ""
msgid "There is currently a single intrinsic mapping type:"
msgstr ""
msgid "Dictionaries"
msgstr ""
msgid "These represent finite sets of objects indexed by nearly arbitrary values. The only types of values not acceptable as keys are values containing lists or dictionaries or other mutable types that are compared by value rather than by object identity, the reason being that the efficient implementation of dictionaries requires a key's hash value to remain constant. Numeric types used for keys obey the normal rules for numeric comparison: if two numbers compare equal (e.g., ``1`` and ``1.0``) then they can be used interchangeably to index the same dictionary entry."
msgstr ""
msgid "Dictionaries preserve insertion order, meaning that keys will be produced in the same order they were added sequentially over the dictionary. Replacing an existing key does not change the order, however removing a key and re-inserting it will add it to the end instead of keeping its old place."
msgstr ""
msgid "Dictionaries are mutable; they can be created by the ``{}`` notation (see section :ref:`dict`)."
msgstr ""
msgid "The extension modules :mod:`dbm.ndbm` and :mod:`dbm.gnu` provide additional examples of mapping types, as does the :mod:`collections` module."
msgstr ""
msgid "Dictionaries did not preserve insertion order in versions of Python before 3.6. In CPython 3.6, insertion order was preserved, but it was considered an implementation detail at that time rather than a language guarantee."
msgstr ""
msgid "Callable types"
msgstr ""
msgid "These are the types to which the function call operation (see section :ref:`calls`) can be applied:"
msgstr ""
msgid "User-defined functions"
msgstr ""
msgid "A user-defined function object is created by a function definition (see section :ref:`function`). It should be called with an argument list containing the same number of items as the function's formal parameter list."
msgstr ""
msgid "Special read-only attributes"
msgstr ""
msgid "Attribute"
msgstr ""
msgid "Meaning"
msgstr ""
msgid "A reference to the :class:`dictionary <dict>` that holds the function's builtins namespace."
msgstr ""
msgid "A reference to the :class:`dictionary <dict>` that holds the function's :ref:`global variables <naming>` -- the global namespace of the module in which the function was defined."
msgstr ""
msgid "``None`` or a :class:`tuple` of cells that contain bindings for the names specified in the :attr:`~codeobject.co_freevars` attribute of the function's :attr:`code object <function.__code__>`."
msgstr ""
msgid "A cell object has the attribute ``cell_contents``. This can be used to get the value of the cell, as well as set the value."
msgstr ""
msgid "Special writable attributes"
msgstr ""
msgid "Most of these attributes check the type of the assigned value:"
msgstr ""
msgid "The function's documentation string, or ``None`` if unavailable."
msgstr ""
msgid "The function's name. See also: :attr:`__name__ attributes <definition.__name__>`."
msgstr ""
msgid "The function's :term:`qualified name`. See also: :attr:`__qualname__ attributes <definition.__qualname__>`."
msgstr ""
msgid "The name of the module the function was defined in, or ``None`` if unavailable."
msgstr ""
msgid "A :class:`tuple` containing default :term:`parameter` values for those parameters that have defaults, or ``None`` if no parameters have a default value."
msgstr ""
msgid "The :ref:`code object <code-objects>` representing the compiled function body."
msgstr ""
msgid "The namespace supporting arbitrary function attributes. See also: :attr:`__dict__ attributes <object.__dict__>`."
msgstr ""
msgid "A :class:`dictionary <dict>` containing annotations of :term:`parameters <parameter>`. The keys of the dictionary are the parameter names, and ``'return'`` for the return annotation, if provided. See also: :attr:`object.__annotations__`."
msgstr ""
msgid "Annotations are now :ref:`lazily evaluated <lazy-evaluation>`. See :pep:`649`."
msgstr ""
msgid "The :term:`annotate function` for this function, or ``None`` if the function has no annotations. See :attr:`object.__annotate__`."
msgstr ""
msgid "A :class:`dictionary <dict>` containing defaults for keyword-only :term:`parameters <parameter>`."
msgstr ""
msgid "A :class:`tuple` containing the :ref:`type parameters <type-params>` of a :ref:`generic function <generic-functions>`."
msgstr ""
msgid "Function objects also support getting and setting arbitrary attributes, which can be used, for example, to attach metadata to functions. Regular attribute dot-notation is used to get and set such attributes."
msgstr ""
msgid "CPython's current implementation only supports function attributes on user-defined functions. Function attributes on :ref:`built-in functions <builtin-functions>` may be supported in the future."
msgstr ""
msgid "Additional information about a function's definition can be retrieved from its :ref:`code object <code-objects>` (accessible via the :attr:`~function.__code__` attribute)."
msgstr ""
msgid "Instance methods"
msgstr ""
msgid "An instance method object combines a class, a class instance and any callable object (normally a user-defined function)."
msgstr ""
msgid "Special read-only attributes:"
msgstr ""
msgid "Refers to the class instance object to which the method is :ref:`bound <method-binding>`"
msgstr ""
msgid "Refers to the original :ref:`function object <user-defined-funcs>`"
msgstr ""
msgid "The method's documentation (same as :attr:`method.__func__.__doc__ <function.__doc__>`). A :class:`string <str>` if the original function had a docstring, else ``None``."
msgstr ""
msgid "The name of the method (same as :attr:`method.__func__.__name__ <function.__name__>`)"
msgstr ""
msgid "The name of the module the method was defined in, or ``None`` if unavailable."
msgstr ""
msgid "Methods also support accessing (but not setting) the arbitrary function attributes on the underlying :ref:`function object <user-defined-funcs>`."
msgstr ""
msgid "User-defined method objects may be created when getting an attribute of a class (perhaps via an instance of that class), if that attribute is a user-defined :ref:`function object <user-defined-funcs>` or a :class:`classmethod` object."
msgstr ""
msgid "When an instance method object is created by retrieving a user-defined :ref:`function object <user-defined-funcs>` from a class via one of its instances, its :attr:`~method.__self__` attribute is the instance, and the method object is said to be *bound*. The new method's :attr:`~method.__func__` attribute is the original function object."
msgstr ""
msgid "When an instance method object is created by retrieving a :class:`classmethod` object from a class or instance, its :attr:`~method.__self__` attribute is the class itself, and its :attr:`~method.__func__` attribute is the function object underlying the class method."
msgstr ""
msgid "When an instance method object is called, the underlying function (:attr:`~method.__func__`) is called, inserting the class instance (:attr:`~method.__self__`) in front of the argument list. For instance, when :class:`!C` is a class which contains a definition for a function :meth:`!f`, and ``x`` is an instance of :class:`!C`, calling ``x.f(1)`` is equivalent to calling ``C.f(x, 1)``."
msgstr ""
msgid "When an instance method object is derived from a :class:`classmethod` object, the \"class instance\" stored in :attr:`~method.__self__` will actually be the class itself, so that calling either ``x.f(1)`` or ``C.f(1)`` is equivalent to calling ``f(C,1)`` where ``f`` is the underlying function."
msgstr ""
msgid "It is important to note that user-defined functions which are attributes of a class instance are not converted to bound methods; this *only* happens when the function is an attribute of the class."
msgstr ""
msgid "Generator functions"
msgstr ""
msgid "A function or method which uses the :keyword:`yield` statement (see section :ref:`yield`) is called a :dfn:`generator function`. Such a function, when called, always returns an :term:`iterator` object which can be used to execute the body of the function: calling the iterator's :meth:`iterator.__next__` method will cause the function to execute until it provides a value using the :keyword:`!yield` statement. When the function executes a :keyword:`return` statement or falls off the end, a :exc:`StopIteration` exception is raised and the iterator will have reached the end of the set of values to be returned."
msgstr ""
msgid "Coroutine functions"
msgstr ""
msgid "A function or method which is defined using :keyword:`async def` is called a :dfn:`coroutine function`. Such a function, when called, returns a :term:`coroutine` object. It may contain :keyword:`await` expressions, as well as :keyword:`async with` and :keyword:`async for` statements. See also the :ref:`coroutine-objects` section."
msgstr ""
msgid "Asynchronous generator functions"
msgstr ""
msgid "A function or method which is defined using :keyword:`async def` and which uses the :keyword:`yield` statement is called a :dfn:`asynchronous generator function`. Such a function, when called, returns an :term:`asynchronous iterator` object which can be used in an :keyword:`async for` statement to execute the body of the function."
msgstr ""
msgid "Calling the asynchronous iterator's :meth:`aiterator.__anext__ <object.__anext__>` method will return an :term:`awaitable` which when awaited will execute until it provides a value using the :keyword:`yield` expression. When the function executes an empty :keyword:`return` statement or falls off the end, a :exc:`StopAsyncIteration` exception is raised and the asynchronous iterator will have reached the end of the set of values to be yielded."
msgstr ""
msgid "Built-in functions"
msgstr ""
msgid "A built-in function object is a wrapper around a C function. Examples of built-in functions are :func:`len` and :func:`math.sin` (:mod:`math` is a standard built-in module). The number and type of the arguments are determined by the C function. Special read-only attributes:"
msgstr ""
msgid ":attr:`!__doc__` is the function's documentation string, or ``None`` if unavailable. See :attr:`function.__doc__`."
msgstr ""
msgid ":attr:`!__name__` is the function's name. See :attr:`function.__name__`."
msgstr ""
msgid ":attr:`!__self__` is set to ``None`` (but see the next item)."
msgstr ""
msgid ":attr:`!__module__` is the name of the module the function was defined in or ``None`` if unavailable. See :attr:`function.__module__`."
msgstr ""
msgid "Built-in methods"
msgstr ""
msgid "This is really a different disguise of a built-in function, this time containing an object passed to the C function as an implicit extra argument. An example of a built-in method is ``alist.append()``, assuming *alist* is a list object. In this case, the special read-only attribute :attr:`!__self__` is set to the object denoted by *alist*. (The attribute has the same semantics as it does with :attr:`other instance methods <method.__self__>`.)"
msgstr ""
msgid "Classes"
msgstr ""
msgid "Classes are callable. These objects normally act as factories for new instances of themselves, but variations are possible for class types that override :meth:`~object.__new__`. The arguments of the call are passed to :meth:`!__new__` and, in the typical case, to :meth:`~object.__init__` to initialize the new instance."
msgstr ""
msgid "Class Instances"
msgstr ""
msgid "Instances of arbitrary classes can be made callable by defining a :meth:`~object.__call__` method in their class."
msgstr ""
msgid "Modules"
msgstr ""
msgid "Modules are a basic organizational unit of Python code, and are created by the :ref:`import system <importsystem>` as invoked either by the :keyword:`import` statement, or by calling functions such as :func:`importlib.import_module` and built-in :func:`__import__`. A module object has a namespace implemented by a :class:`dictionary <dict>` object (this is the dictionary referenced by the :attr:`~function.__globals__` attribute of functions defined in the module). Attribute references are translated to lookups in this dictionary, e.g., ``m.x`` is equivalent to ``m.__dict__[\"x\"]``. A module object does not contain the code object used to initialize the module (since it isn't needed once the initialization is done)."
msgstr ""
msgid "Attribute assignment updates the module's namespace dictionary, e.g., ``m.x = 1`` is equivalent to ``m.__dict__[\"x\"] = 1``."
msgstr ""
msgid "Import-related attributes on module objects"
msgstr ""
msgid "Module objects have the following attributes that relate to the :ref:`import system <importsystem>`. When a module is created using the machinery associated with the import system, these attributes are filled in based on the module's :term:`spec <module spec>`, before the :term:`loader` executes and loads the module."
msgstr ""
msgid "To create a module dynamically rather than using the import system, it's recommended to use :func:`importlib.util.module_from_spec`, which will set the various import-controlled attributes to appropriate values. It's also possible to use the :class:`types.ModuleType` constructor to create modules directly, but this technique is more error-prone, as most attributes must be manually set on the module object after it has been created when using this approach."
msgstr ""
msgid "With the exception of :attr:`~module.__name__`, it is **strongly** recommended that you rely on :attr:`~module.__spec__` and its attributes instead of any of the other individual attributes listed in this subsection. Note that updating an attribute on :attr:`!__spec__` will not update the corresponding attribute on the module itself:"
msgstr ""
msgid ""
">>> import typing\n"
">>> typing.__name__, typing.__spec__.name\n"
"('typing', 'typing')\n"
">>> typing.__spec__.name = 'spelling'\n"
">>> typing.__name__, typing.__spec__.name\n"
"('typing', 'spelling')\n"
">>> typing.__name__ = 'keyboard_smashing'\n"
">>> typing.__name__, typing.__spec__.name\n"
"('keyboard_smashing', 'spelling')"
msgstr ""
msgid "The name used to uniquely identify the module in the import system. For a directly executed module, this will be set to ``\"__main__\"``."
msgstr ""
msgid "This attribute must be set to the fully qualified name of the module. It is expected to match the value of :attr:`module.__spec__.name <importlib.machinery.ModuleSpec.name>`."
msgstr ""
msgid "A record of the module's import-system-related state."
msgstr ""
msgid "Set to the :class:`module spec <importlib.machinery.ModuleSpec>` that was used when importing the module. See :ref:`module-specs` for more details."
msgstr ""
msgid "The :term:`package` a module belongs to."
msgstr ""
msgid "If the module is top-level (that is, not a part of any specific package) then the attribute should be set to ``''`` (the empty string). Otherwise, it should be set to the name of the module's package (which can be equal to :attr:`module.__name__` if the module itself is a package). See :pep:`366` for further details."
msgstr ""
msgid "This attribute is used instead of :attr:`~module.__name__` to calculate explicit relative imports for main modules. It defaults to ``None`` for modules created dynamically using the :class:`types.ModuleType` constructor; use :func:`importlib.util.module_from_spec` instead to ensure the attribute is set to a :class:`str`."
msgstr ""
msgid "It is **strongly** recommended that you use :attr:`module.__spec__.parent <importlib.machinery.ModuleSpec.parent>` instead of :attr:`!module.__package__`. :attr:`__package__` is now only used as a fallback if :attr:`!__spec__.parent` is not set, and this fallback path is deprecated."
msgstr ""
msgid "This attribute now defaults to ``None`` for modules created dynamically using the :class:`types.ModuleType` constructor. Previously the attribute was optional."
msgstr ""
msgid "The value of :attr:`!__package__` is expected to be the same as :attr:`__spec__.parent <importlib.machinery.ModuleSpec.parent>`. :attr:`__package__` is now only used as a fallback during import resolution if :attr:`!__spec__.parent` is not defined."
msgstr ""
msgid ":exc:`ImportWarning` is raised if an import resolution falls back to :attr:`!__package__` instead of :attr:`__spec__.parent <importlib.machinery.ModuleSpec.parent>`."
msgstr ""
msgid "Raise :exc:`DeprecationWarning` instead of :exc:`ImportWarning` when falling back to :attr:`!__package__` during import resolution."
msgstr ""
msgid ":attr:`!__package__` will cease to be set or taken into consideration by the import system or standard library."
msgstr ""
msgid "The :term:`loader` object that the import machinery used to load the module."
msgstr ""
msgid "This attribute is mostly useful for introspection, but can be used for additional loader-specific functionality, for example getting data associated with a loader."
msgstr ""
msgid ":attr:`!__loader__` defaults to ``None`` for modules created dynamically using the :class:`types.ModuleType` constructor; use :func:`importlib.util.module_from_spec` instead to ensure the attribute is set to a :term:`loader` object."
msgstr ""
msgid "It is **strongly** recommended that you use :attr:`module.__spec__.loader <importlib.machinery.ModuleSpec.loader>` instead of :attr:`!module.__loader__`."
msgstr ""
msgid "Setting :attr:`!__loader__` on a module while failing to set :attr:`!__spec__.loader` is deprecated. In Python 3.16, :attr:`!__loader__` will cease to be set or taken into consideration by the import system or the standard library."
msgstr ""
msgid "A (possibly empty) :term:`sequence` of strings enumerating the locations where the package's submodules will be found. Non-package modules should not have a :attr:`!__path__` attribute. See :ref:`package-path-rules` for more details."
msgstr ""
msgid "It is **strongly** recommended that you use :attr:`module.__spec__.submodule_search_locations <importlib.machinery.ModuleSpec.submodule_search_locations>` instead of :attr:`!module.__path__`."
msgstr ""
msgid ":attr:`!__file__` and :attr:`!__cached__` are both optional attributes that may or may not be set. Both attributes should be a :class:`str` when they are available."
msgstr ""
msgid ":attr:`!__file__` indicates the pathname of the file from which the module was loaded (if loaded from a file), or the pathname of the shared library file for extension modules loaded dynamically from a shared library. It might be missing for certain types of modules, such as C modules that are statically linked into the interpreter, and the :ref:`import system <importsystem>` may opt to leave it unset if it has no semantic meaning (for example, a module loaded from a database)."
msgstr ""
msgid "If :attr:`!__file__` is set then the :attr:`!__cached__` attribute might also be set, which is the path to any compiled version of the code (for example, a byte-compiled file). The file does not need to exist to set this attribute; the path can simply point to where the compiled file *would* exist (see :pep:`3147`)."
msgstr ""
msgid "Note that :attr:`!__cached__` may be set even if :attr:`!__file__` is not set. However, that scenario is quite atypical. Ultimately, the :term:`loader` is what makes use of the module spec provided by the :term:`finder` (from which :attr:`!__file__` and :attr:`!__cached__` are derived). So if a loader can load from a cached module but otherwise does not load from a file, that atypical scenario may be appropriate."
msgstr ""
msgid "It is **strongly** recommended that you use :attr:`module.__spec__.cached <importlib.machinery.ModuleSpec.cached>` instead of :attr:`!module.__cached__`."
msgstr ""
msgid "Setting :attr:`!__cached__` on a module while failing to set :attr:`!__spec__.cached` is deprecated. In Python 3.15, :attr:`!__cached__` will cease to be set or taken into consideration by the import system or standard library."
msgstr ""
msgid "Other writable attributes on module objects"
msgstr ""
msgid "As well as the import-related attributes listed above, module objects also have the following writable attributes:"
msgstr ""
msgid "The module's documentation string, or ``None`` if unavailable. See also: :attr:`__doc__ attributes <definition.__doc__>`."
msgstr ""
msgid "A dictionary containing :term:`variable annotations <variable annotation>` collected during module body execution. For best practices on working with :attr:`!__annotations__`, see :mod:`annotationlib`."
msgstr ""
msgid "The :term:`annotate function` for this module, or ``None`` if the module has no annotations. See also: :attr:`~object.__annotate__` attributes."
msgstr ""
msgid "Module dictionaries"
msgstr ""
msgid "Module objects also have the following special read-only attribute:"
msgstr ""
msgid "The module's namespace as a dictionary object. Uniquely among the attributes listed here, :attr:`!__dict__` cannot be accessed as a global variable from within a module; it can only be accessed as an attribute on module objects."
msgstr ""
msgid "Because of the way CPython clears module dictionaries, the module dictionary will be cleared when the module falls out of scope even if the dictionary still has live references. To avoid this, copy the dictionary or keep the module around while using its dictionary directly."
msgstr ""
msgid "Custom classes"
msgstr ""
msgid "Custom class types are typically created by class definitions (see section :ref:`class`). A class has a namespace implemented by a dictionary object. Class attribute references are translated to lookups in this dictionary, e.g., ``C.x`` is translated to ``C.__dict__[\"x\"]`` (although there are a number of hooks which allow for other means of locating attributes). When the attribute name is not found there, the attribute search continues in the base classes. This search of the base classes uses the C3 method resolution order which behaves correctly even in the presence of 'diamond' inheritance structures where there are multiple inheritance paths leading back to a common ancestor. Additional details on the C3 MRO used by Python can be found at :ref:`python_2.3_mro`."
msgstr ""
msgid "When a class attribute reference (for class :class:`!C`, say) would yield a class method object, it is transformed into an instance method object whose :attr:`~method.__self__` attribute is :class:`!C`. When it would yield a :class:`staticmethod` object, it is transformed into the object wrapped by the static method object. See section :ref:`descriptors` for another way in which attributes retrieved from a class may differ from those actually contained in its :attr:`~object.__dict__`."
msgstr ""
msgid "Class attribute assignments update the class's dictionary, never the dictionary of a base class."
msgstr ""
msgid "A class object can be called (see above) to yield a class instance (see below)."
msgstr ""
msgid "Special attributes"
msgstr ""
msgid "The class's name. See also: :attr:`__name__ attributes <definition.__name__>`."
msgstr ""
msgid "The class's :term:`qualified name`. See also: :attr:`__qualname__ attributes <definition.__qualname__>`."
msgstr ""
msgid "The name of the module in which the class was defined."
msgstr ""
msgid "A :class:`mapping proxy <types.MappingProxyType>` providing a read-only view of the class's namespace. See also: :attr:`__dict__ attributes <object.__dict__>`."
msgstr ""
msgid "A :class:`tuple` containing the class's bases. In most cases, for a class defined as ``class X(A, B, C)``, ``X.__bases__`` will be exactly equal to ``(A, B, C)``."
msgstr ""
msgid "The single base class in the inheritance chain that is responsible for the memory layout of instances. This attribute corresponds to :c:member:`~PyTypeObject.tp_base` at the C level."
msgstr ""
msgid "The class's documentation string, or ``None`` if undefined. Not inherited by subclasses."
msgstr ""
msgid "A dictionary containing :term:`variable annotations <variable annotation>` collected during class body execution. See also: :attr:`__annotations__ attributes <object.__annotations__>`."
msgstr ""
msgid "For best practices on working with :attr:`~object.__annotations__`, please see :mod:`annotationlib`. Use :func:`annotationlib.get_annotations` instead of accessing this attribute directly."
msgstr ""
msgid "Accessing the :attr:`!__annotations__` attribute directly on a class object may return annotations for the wrong class, specifically in certain cases where the class, its base class, or a metaclass is defined under ``from __future__ import annotations``. See :pep:`749 <749#pep749-metaclasses>` for details."
msgstr ""
msgid "This attribute does not exist on certain builtin classes. On user-defined classes without ``__annotations__``, it is an empty dictionary."
msgstr ""
msgid "The :term:`annotate function` for this class, or ``None`` if the class has no annotations. See also: :attr:`__annotate__ attributes <object.__annotate__>`."
msgstr ""
msgid "A :class:`tuple` containing the :ref:`type parameters <type-params>` of a :ref:`generic class <generic-classes>`."
msgstr ""
msgid "A :class:`tuple` containing names of attributes of this class which are assigned through ``self.X`` from any function in its body."
msgstr ""
msgid "The line number of the first line of the class definition, including decorators. Setting the :attr:`~type.__module__` attribute removes the :attr:`!__firstlineno__` item from the type's dictionary."
msgstr ""
msgid "The :class:`tuple` of classes that are considered when looking for base classes during method resolution."
msgstr ""
msgid "Special methods"
msgstr ""
msgid "In addition to the special attributes described above, all Python classes also have the following two methods available:"
msgstr ""
msgid "This method can be overridden by a metaclass to customize the method resolution order for its instances. It is called at class instantiation, and its result is stored in :attr:`~type.__mro__`."
msgstr ""
msgid "Each class keeps a list of weak references to its immediate subclasses. This method returns a list of all those references still alive. The list is in definition order. Example:"
msgstr ""
msgid ""
">>> class A: pass\n"
">>> class B(A): pass\n"
">>> A.__subclasses__()\n"
"[<class 'B'>]"
msgstr ""
msgid "Class instances"
msgstr ""
msgid "A class instance is created by calling a class object (see above). A class instance has a namespace implemented as a dictionary which is the first place in which attribute references are searched. When an attribute is not found there, and the instance's class has an attribute by that name, the search continues with the class attributes. If a class attribute is found that is a user-defined function object, it is transformed into an instance method object whose :attr:`~method.__self__` attribute is the instance. Static method and class method objects are also transformed; see above under \"Classes\". See section :ref:`descriptors` for another way in which attributes of a class retrieved via its instances may differ from the objects actually stored in the class's :attr:`~object.__dict__`. If no class attribute is found, and the object's class has a :meth:`~object.__getattr__` method, that is called to satisfy the lookup."
msgstr ""
msgid "Attribute assignments and deletions update the instance's dictionary, never a class's dictionary. If the class has a :meth:`~object.__setattr__` or :meth:`~object.__delattr__` method, this is called instead of updating the instance dictionary directly."
msgstr ""
msgid "Class instances can pretend to be numbers, sequences, or mappings if they have methods with certain special names. See section :ref:`specialnames`."
msgstr ""
msgid "The class to which a class instance belongs."
msgstr ""
msgid "A dictionary or other mapping object used to store an object's (writable) attributes. Not all instances have a :attr:`!__dict__` attribute; see the section on :ref:`slots` for more details."
msgstr ""
msgid "I/O objects (also known as file objects)"
msgstr ""
msgid "A :term:`file object` represents an open file. Various shortcuts are available to create file objects: the :func:`open` built-in function, and also :func:`os.popen`, :func:`os.fdopen`, and the :meth:`~socket.socket.makefile` method of socket objects (and perhaps by other functions or methods provided by extension modules)."
msgstr ""
msgid "File objects implement common methods, listed below, to simplify usage in generic code. They are expected to be :ref:`context-managers`."
msgstr ""
msgid "The objects ``sys.stdin``, ``sys.stdout`` and ``sys.stderr`` are initialized to file objects corresponding to the interpreter's standard input, output and error streams; they are all open in text mode and therefore follow the interface defined by the :class:`io.TextIOBase` abstract class."
msgstr ""
msgid "Retrieve up to *size* data from the file. As a convenience if *size* is unspecified or -1 retrieve all data available."
msgstr ""
msgid "Store *data* to the file."
msgstr ""
msgid "Flush any buffers and close the underlying file."
msgstr ""
msgid "Internal types"
msgstr ""
msgid "A few types used internally by the interpreter are exposed to the user. Their definitions may change with future versions of the interpreter, but they are mentioned here for completeness."
msgstr ""
msgid "Code objects"
msgstr ""
msgid "Code objects represent *byte-compiled* executable Python code, or :term:`bytecode`. The difference between a code object and a function object is that the function object contains an explicit reference to the function's globals (the module in which it was defined), while a code object contains no context; also the default argument values are stored in the function object, not in the code object (because they represent values calculated at run-time). Unlike function objects, code objects are immutable and contain no references (directly or indirectly) to mutable objects."
msgstr ""
msgid "The function name"
msgstr ""
msgid "The fully qualified function name"
msgstr ""
msgid "The total number of positional :term:`parameters <parameter>` (including positional-only parameters and parameters with default values) that the function has"
msgstr ""
msgid "The number of positional-only :term:`parameters <parameter>` (including arguments with default values) that the function has"
msgstr ""
msgid "The number of keyword-only :term:`parameters <parameter>` (including arguments with default values) that the function has"
msgstr ""
msgid "The number of :ref:`local variables <naming>` used by the function (including parameters)"
msgstr ""
msgid "A :class:`tuple` containing the names of the local variables in the function (starting with the parameter names)"
msgstr ""
msgid "A :class:`tuple` containing the names of :ref:`local variables <naming>` that are referenced from at least one :term:`nested scope` inside the function"
msgstr ""
msgid "A :class:`tuple` containing the names of :term:`free (closure) variables <closure variable>` that a :term:`nested scope` references in an outer scope. See also :attr:`function.__closure__`."
msgstr ""
msgid "Note: references to global and builtin names are *not* included."
msgstr ""
msgid "A string representing the sequence of :term:`bytecode` instructions in the function"
msgstr ""
msgid "A :class:`tuple` containing the literals used by the :term:`bytecode` in the function"
msgstr ""
msgid "A :class:`tuple` containing the names used by the :term:`bytecode` in the function"
msgstr ""
msgid "The name of the file from which the code was compiled"
msgstr ""
msgid "The line number of the first line of the function"
msgstr ""
msgid "A string encoding the mapping from :term:`bytecode` offsets to line numbers. For details, see the source code of the interpreter."
msgstr ""
msgid "This attribute of code objects is deprecated, and may be removed in Python 3.15."
msgstr ""
msgid "The required stack size of the code object"
msgstr ""
msgid "An :class:`integer <int>` encoding a number of flags for the interpreter."
msgstr ""
msgid "The following flag bits are defined for :attr:`~codeobject.co_flags`: bit ``0x04`` is set if the function uses the ``*arguments`` syntax to accept an arbitrary number of positional arguments; bit ``0x08`` is set if the function uses the ``**keywords`` syntax to accept arbitrary keyword arguments; bit ``0x20`` is set if the function is a generator. See :ref:`inspect-module-co-flags` for details on the semantics of each flags that might be present."
msgstr ""
msgid "Future feature declarations (for example, ``from __future__ import division``) also use bits in :attr:`~codeobject.co_flags` to indicate whether a code object was compiled with a particular feature enabled. See :attr:`~__future__._Feature.compiler_flag`."
msgstr ""
msgid "Other bits in :attr:`~codeobject.co_flags` are reserved for internal use."
msgstr ""
msgid "If a code object represents a function and has a docstring, the :data:`~inspect.CO_HAS_DOCSTRING` bit is set in :attr:`~codeobject.co_flags` and the first item in :attr:`~codeobject.co_consts` is the docstring of the function."
msgstr ""
msgid "Methods on code objects"
msgstr ""
msgid "Returns an iterable over the source code positions of each :term:`bytecode` instruction in the code object."
msgstr ""
msgid "The iterator returns :class:`tuple`\\s containing the ``(start_line, end_line, start_column, end_column)``. The *i-th* tuple corresponds to the position of the source code that compiled to the *i-th* code unit. Column information is 0-indexed utf-8 byte offsets on the given source line."
msgstr ""
msgid "This positional information can be missing. A non-exhaustive lists of cases where this may happen:"
msgstr ""
msgid "Running the interpreter with :option:`-X` ``no_debug_ranges``."
msgstr ""
msgid "Loading a pyc file compiled while using :option:`-X` ``no_debug_ranges``."
msgstr ""
msgid "Position tuples corresponding to artificial instructions."
msgstr ""
msgid "Line and column numbers that can't be represented due to implementation specific limitations."
msgstr ""
msgid "When this occurs, some or all of the tuple elements can be :const:`None`."
msgstr ""
msgid "This feature requires storing column positions in code objects which may result in a small increase of disk usage of compiled Python files or interpreter memory usage. To avoid storing the extra information and/or deactivate printing the extra traceback information, the :option:`-X` ``no_debug_ranges`` command line flag or the :envvar:`PYTHONNODEBUGRANGES` environment variable can be used."
msgstr ""
msgid "Returns an iterator that yields information about successive ranges of :term:`bytecode`\\s. Each item yielded is a ``(start, end, lineno)`` :class:`tuple`:"
msgstr ""
msgid "``start`` (an :class:`int`) represents the offset (inclusive) of the start of the :term:`bytecode` range"
msgstr ""
msgid "``end`` (an :class:`int`) represents the offset (exclusive) of the end of the :term:`bytecode` range"
msgstr ""
msgid "``lineno`` is an :class:`int` representing the line number of the :term:`bytecode` range, or ``None`` if the bytecodes in the given range have no line number"
msgstr ""
msgid "The items yielded will have the following properties:"
msgstr ""
msgid "The first range yielded will have a ``start`` of 0."
msgstr ""
msgid "The ``(start, end)`` ranges will be non-decreasing and consecutive. That is, for any pair of :class:`tuple`\\s, the ``start`` of the second will be equal to the ``end`` of the first."
msgstr ""
msgid "No range will be backwards: ``end >= start`` for all triples."
msgstr ""
msgid "The last :class:`tuple` yielded will have ``end`` equal to the size of the :term:`bytecode`."
msgstr ""
msgid "Zero-width ranges, where ``start == end``, are allowed. Zero-width ranges are used for lines that are present in the source code, but have been eliminated by the :term:`bytecode` compiler."
msgstr ""
msgid ":pep:`626` - Precise line numbers for debugging and other tools."
msgstr ""
msgid "The PEP that introduced the :meth:`!co_lines` method."
msgstr ""
msgid "Return a copy of the code object with new values for the specified fields."
msgstr ""
msgid "Code objects are also supported by the generic function :func:`copy.replace`."
msgstr ""
msgid "Frame objects"
msgstr ""
msgid "Frame objects represent execution frames. They may occur in :ref:`traceback objects <traceback-objects>`, and are also passed to registered trace functions."
msgstr ""
msgid "Points to the previous stack frame (towards the caller), or ``None`` if this is the bottom stack frame"
msgstr ""
msgid "The :ref:`code object <code-objects>` being executed in this frame. Accessing this attribute raises an :ref:`auditing event <auditing>` ``object.__getattr__`` with arguments ``obj`` and ``\"f_code\"``."
msgstr ""
msgid "The mapping used by the frame to look up :ref:`local variables <naming>`. If the frame refers to an :term:`optimized scope`, this may return a write-through proxy object."
msgstr ""
msgid "Return a proxy for optimized scopes."
msgstr ""
msgid "The dictionary used by the frame to look up :ref:`global variables <naming>`"
msgstr ""
msgid "The dictionary used by the frame to look up :ref:`built-in (intrinsic) names <naming>`"
msgstr ""
msgid "The \"precise instruction\" of the frame object (this is an index into the :term:`bytecode` string of the :ref:`code object <code-objects>`)"
msgstr ""
msgid "The :term:`generator` or :term:`coroutine` object that owns this frame, or ``None`` if the frame is a normal function."
msgstr ""
msgid "If not ``None``, this is a function called for various events during code execution (this is used by debuggers). Normally an event is triggered for each new source line (see :attr:`~frame.f_trace_lines`)."
msgstr ""
msgid "Set this attribute to :const:`False` to disable triggering a tracing event for each source line."
msgstr ""
msgid "Set this attribute to :const:`True` to allow per-opcode events to be requested. Note that this may lead to undefined interpreter behaviour if exceptions raised by the trace function escape to the function being traced."
msgstr ""
msgid "The current line number of the frame -- writing to this from within a trace function jumps to the given line (only for the bottom-most frame). A debugger can implement a Jump command (aka Set Next Statement) by writing to this attribute."
msgstr ""
msgid "Frame object methods"
msgstr ""
msgid "Frame objects support one method:"
msgstr ""
msgid "This method clears all references to :ref:`local variables <naming>` held by the frame. Also, if the frame belonged to a :term:`generator`, the generator is finalized. This helps break reference cycles involving frame objects (for example when catching an :ref:`exception <bltin-exceptions>` and storing its :ref:`traceback <traceback-objects>` for later use)."
msgstr ""
msgid ":exc:`RuntimeError` is raised if the frame is currently executing or suspended."
msgstr ""
msgid "Attempting to clear a suspended frame raises :exc:`RuntimeError` (as has always been the case for executing frames)."
msgstr ""
msgid "Traceback objects"
msgstr ""
msgid "Traceback objects represent the stack trace of an :ref:`exception <tut-errors>`. A traceback object is implicitly created when an exception occurs, and may also be explicitly created by calling :class:`types.TracebackType`."
msgstr ""
msgid "Traceback objects can now be explicitly instantiated from Python code."
msgstr ""
msgid "For implicitly created tracebacks, when the search for an exception handler unwinds the execution stack, at each unwound level a traceback object is inserted in front of the current traceback. When an exception handler is entered, the stack trace is made available to the program. (See section :ref:`try`.) It is accessible as the third item of the tuple returned by :func:`sys.exc_info`, and as the :attr:`~BaseException.__traceback__` attribute of the caught exception."
msgstr ""
msgid "When the program contains no suitable handler, the stack trace is written (nicely formatted) to the standard error stream; if the interpreter is interactive, it is also made available to the user as :data:`sys.last_traceback`."
msgstr ""
msgid "For explicitly created tracebacks, it is up to the creator of the traceback to determine how the :attr:`~traceback.tb_next` attributes should be linked to form a full stack trace."
msgstr ""
msgid "Points to the execution :ref:`frame <frame-objects>` of the current level."
msgstr ""
msgid "Accessing this attribute raises an :ref:`auditing event <auditing>` ``object.__getattr__`` with arguments ``obj`` and ``\"tb_frame\"``."
msgstr ""
msgid "Gives the line number where the exception occurred"
msgstr ""
msgid "Indicates the \"precise instruction\"."
msgstr ""
msgid "The line number and last instruction in the traceback may differ from the line number of its :ref:`frame object <frame-objects>` if the exception occurred in a :keyword:`try` statement with no matching except clause or with a :keyword:`finally` clause."
msgstr ""
msgid "The special writable attribute :attr:`!tb_next` is the next level in the stack trace (towards the frame where the exception occurred), or ``None`` if there is no next level."
msgstr ""
msgid "This attribute is now writable"
msgstr ""
msgid "Slice objects"
msgstr ""
msgid "Slice objects are used to represent slices for :meth:`~object.__getitem__` methods. They are also created by the built-in :func:`slice` function."
msgstr ""
msgid "Special read-only attributes: :attr:`~slice.start` is the lower bound; :attr:`~slice.stop` is the upper bound; :attr:`~slice.step` is the step value; each is ``None`` if omitted. These attributes can have any type."
msgstr ""
msgid "Slice objects support one method:"