Skip to content
Navigation Menu
{{ message }}
-
-
Notifications
You must be signed in to change notification settings - Fork 14
Expand file tree
/
Copy pathstructures.po
More file actions
1024 lines (812 loc) · 30.1 KB
/
Copy pathstructures.po
File metadata and controls
1024 lines (812 loc) · 30.1 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:
# python-doc bot, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-06-21 15:47+0000\n"
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
"Last-Translator: python-doc bot, 2025\n"
"Language-Team: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "
"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "
"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
msgid "Common Object Structures"
msgstr "Wspólne struktury obiektów"
msgid ""
"There are a large number of structures which are used in the definition of "
"object types for Python. This section describes these structures and how "
"they are used."
msgstr ""
"Istnieje duża liczba struktur, które są używane przy definiowaniu rodzajów "
"obiektów w Pythonie. Ten rozdział opisuje te struktury i jak są one używane."
msgid "Base object types and macros"
msgstr ""
msgid ""
"All Python objects ultimately share a small number of fields at the "
"beginning of the object's representation in memory. These are represented "
"by the :c:type:`PyObject` and :c:type:`PyVarObject` types, which are "
"defined, in turn, by the expansions of some macros also used, whether "
"directly or indirectly, in the definition of all other Python objects. "
"Additional macros can be found under :ref:`reference counting "
"<countingrefs>`."
msgstr ""
msgid ""
"All object types are extensions of this type. This is a type which contains "
"the information Python needs to treat a pointer to an object as an object. "
"In a normal \"release\" build, it contains only the object's reference count "
"and a pointer to the corresponding type object. Nothing is actually declared "
"to be a :c:type:`PyObject`, but every pointer to a Python object can be cast "
"to a :c:expr:`PyObject*`."
msgstr ""
msgid ""
"The members must not be accessed directly; instead use macros such as :c:"
"macro:`Py_REFCNT` and :c:macro:`Py_TYPE`."
msgstr ""
msgid ""
"In the :ref:`Stable ABI <stable-abi>` for Free-Threaded Builds (``abi3t``), "
"this struct is opaque; its size and layout may change between Python "
"versions. In Stable ABI for non-free-threaded builds (``abi3``), the :c:"
"member:`!ob_refcnt` and :c:member:`!ob_type` fields are available, but using "
"them directly is discouraged."
msgstr ""
msgid ""
"The object's reference count, as returned by :c:macro:`Py_REFCNT`. Do not "
"use this field directly; instead use functions and macros such as :c:macro:`!"
"Py_REFCNT`, :c:func:`Py_INCREF` and :c:func:`Py_DecRef`."
msgstr ""
msgid ""
"The field type may be different from ``Py_ssize_t``, depending on build "
"configuration and platform."
msgstr ""
msgid ""
"The object's type. Do not use this field directly; use :c:macro:`Py_TYPE` "
"and :c:func:`Py_SET_TYPE` instead."
msgstr ""
msgid ""
"A :ref:`per-object lock <per-object-locks>`, present only in the :term:`free-"
"threaded <free threading>` build (when :c:macro:`Py_GIL_DISABLED` is "
"defined)."
msgstr ""
msgid ""
"This field is **reserved for use by the critical section API** (:c:macro:"
"`Py_BEGIN_CRITICAL_SECTION` / :c:macro:`Py_END_CRITICAL_SECTION`). Do "
"**not** lock it directly with ``PyMutex_Lock``; doing so can cause "
"deadlocks. If you need your own lock, add a separate :c:type:`PyMutex` "
"field to your object struct."
msgstr ""
msgid ""
"An extension of :c:type:`PyObject` that adds the :c:member:`~PyVarObject."
"ob_size` field. This is intended for objects that have some notion of "
"*length*."
msgstr ""
msgid ""
"As with :c:type:`!PyObject`, the members must not be accessed directly; "
"instead use macros such as :c:macro:`Py_SIZE`, :c:macro:`Py_REFCNT` and :c:"
"macro:`Py_TYPE`."
msgstr ""
msgid ""
"In the :ref:`Stable ABI <stable-abi>` for Free-Threaded Builds (``abi3t``), "
"this struct is opaque; its size and layout may change between Python "
"versions. In Stable ABI for non-free-threaded builds (``abi3``), the :c:"
"member:`!ob_base` and :c:member:`!ob_size` fields are available, but using "
"them directly is discouraged."
msgstr ""
msgid ""
"Common object header. Typically, this field is not accessed directly; "
"instead :c:type:`!PyVarObject` can be cast to :c:type:`PyObject`."
msgstr ""
msgid ""
"A size field, whose contents should be considered an object's internal "
"implementation detail."
msgstr ""
msgid "Do not use this field directly; use :c:macro:`Py_SIZE` instead."
msgstr ""
msgid ""
"Object creation functions such as :c:func:`PyObject_NewVar` will generally "
"set this field to the requested size (number of items). After creation, "
"arbitrary values can be stored in :c:member:`!ob_size` using :c:macro:"
"`Py_SET_SIZE`."
msgstr ""
msgid ""
"To get an object's publicly exposed length, as returned by the Python "
"function :py:func:`len`, use :c:func:`PyObject_Length` instead."
msgstr ""
msgid ""
"This is a macro used when declaring new types which represent objects "
"without a varying length. The PyObject_HEAD macro expands to::"
msgstr ""
msgid "PyObject ob_base;"
msgstr ""
msgid "See documentation of :c:type:`PyObject` above."
msgstr ""
msgid ""
"This is a macro used when declaring new types which represent objects with a "
"length that varies from instance to instance. The PyObject_VAR_HEAD macro "
"expands to::"
msgstr ""
msgid "PyVarObject ob_base;"
msgstr ""
msgid "See documentation of :c:type:`PyVarObject` above."
msgstr ""
msgid ""
"The base class of all other objects, the same as :class:`object` in Python."
msgstr ""
msgid ""
"Test if the *x* object is the *y* object, the same as ``x is y`` in Python."
msgstr ""
msgid ""
"Test if an object is the ``None`` singleton, the same as ``x is None`` in "
"Python."
msgstr ""
msgid ""
"Test if an object is the ``True`` singleton, the same as ``x is True`` in "
"Python."
msgstr ""
msgid ""
"Test if an object is the ``False`` singleton, the same as ``x is False`` in "
"Python."
msgstr ""
msgid "Get the type of the Python object *o*."
msgstr ""
msgid ""
"The returned reference is :term:`borrowed <borrowed reference>` from *o*. Do "
"not release it with :c:func:`Py_DECREF` or similar."
msgstr ""
msgid ""
":c:func:`Py_TYPE()` is changed to an inline static function. The parameter "
"type is no longer :c:expr:`const PyObject*`."
msgstr ""
msgid ""
"Return non-zero if the object *o* type is *type*. Return zero otherwise. "
"Equivalent to: ``Py_TYPE(o) == type``."
msgstr ""
msgid ""
"Set the type of object *o* to *type*, without any checking or reference "
"counting."
msgstr ""
msgid ""
"This is a very low-level operation. Consider instead setting the Python "
"attribute :attr:`~object.__class__` using :c:func:`PyObject_SetAttrString` "
"or similar."
msgstr ""
msgid ""
"Note that assigning an incompatible type can lead to undefined behavior."
msgstr ""
msgid ""
"If *type* is a :ref:`heap type <heap-types>`, the caller must create a new "
"reference to it. Similarly, if the old type of *o* is a heap type, the "
"caller must release a reference to that type."
msgstr ""
msgid "Get the :c:member:`~PyVarObject.ob_size` field of *o*."
msgstr ""
msgid ""
":c:func:`Py_SIZE()` is changed to an inline static function. The parameter "
"type is no longer :c:expr:`const PyVarObject*`."
msgstr ""
msgid "Set the :c:member:`~PyVarObject.ob_size` field of *o* to *size*."
msgstr ""
msgid ""
"This is a macro which expands to initialization values for a new :c:type:"
"`PyObject` type. This macro expands to::"
msgstr ""
msgid ""
"_PyObject_EXTRA_INIT\n"
"1, type,"
msgstr ""
msgid ""
"This is a macro which expands to initialization values for a new :c:type:"
"`PyVarObject` type, including the :c:member:`~PyVarObject.ob_size` field. "
"This macro expands to::"
msgstr ""
msgid ""
"_PyObject_EXTRA_INIT\n"
"1, type, size,"
msgstr ""
msgid "Implementing functions and methods"
msgstr ""
msgid ""
"Type of the functions used to implement most Python callables in C. "
"Functions of this type take two :c:expr:`PyObject*` parameters and return "
"one such value. If the return value is ``NULL``, an exception shall have "
"been set. If not ``NULL``, the return value is interpreted as the return "
"value of the function as exposed in Python. The function must return a new "
"reference."
msgstr ""
msgid "The function signature is::"
msgstr ""
msgid ""
"PyObject *PyCFunction(PyObject *self,\n"
" PyObject *args);"
msgstr ""
msgid ""
"Type of the functions used to implement Python callables in C with "
"signature :ref:`METH_VARARGS | METH_KEYWORDS <METH_VARARGS-METH_KEYWORDS>`. "
"The function signature is::"
msgstr ""
msgid ""
"PyObject *PyCFunctionWithKeywords(PyObject *self,\n"
" PyObject *args,\n"
" PyObject *kwargs);"
msgstr ""
msgid ""
"Type of the functions used to implement Python callables in C with "
"signature :c:macro:`METH_FASTCALL`. The function signature is::"
msgstr ""
msgid ""
"PyObject *PyCFunctionFast(PyObject *self,\n"
" PyObject *const *args,\n"
" Py_ssize_t nargs);"
msgstr ""
msgid ""
"Type of the functions used to implement Python callables in C with "
"signature :ref:`METH_FASTCALL | METH_KEYWORDS <METH_FASTCALL-"
"METH_KEYWORDS>`. The function signature is::"
msgstr ""
msgid ""
"PyObject *PyCFunctionFastWithKeywords(PyObject *self,\n"
" PyObject *const *args,\n"
" Py_ssize_t nargs,\n"
" PyObject *kwnames);"
msgstr ""
msgid ""
"Type of the functions used to implement Python callables in C with "
"signature :ref:`METH_METHOD | METH_FASTCALL | METH_KEYWORDS <METH_METHOD-"
"METH_FASTCALL-METH_KEYWORDS>`. The function signature is::"
msgstr ""
msgid ""
"PyObject *PyCMethod(PyObject *self,\n"
" PyTypeObject *defining_class,\n"
" PyObject *const *args,\n"
" Py_ssize_t nargs,\n"
" PyObject *kwnames)"
msgstr ""
msgid ""
"Structure used to describe a method of an extension type. This structure "
"has four fields:"
msgstr ""
msgid "Name of the method."
msgstr ""
msgid "A ``NULL`` *ml_name* marks the end of a :c:type:`!PyMethodDef` array."
msgstr ""
msgid "Pointer to the C implementation."
msgstr ""
msgid "Flags bits indicating how the call should be constructed."
msgstr ""
msgid "Points to the contents of the docstring."
msgstr ""
msgid ""
"The :c:member:`~PyMethodDef.ml_meth` is a C function pointer. The functions "
"may be of different types, but they always return :c:expr:`PyObject*`. If "
"the function is not of the :c:type:`PyCFunction`, the compiler will require "
"a cast in the method table. Even though :c:type:`PyCFunction` defines the "
"first parameter as :c:expr:`PyObject*`, it is common that the method "
"implementation uses the specific C type of the *self* object."
msgstr ""
msgid ""
"The :c:member:`~PyMethodDef.ml_flags` field is a bitfield which can include "
"the following flags. The individual flags indicate either a calling "
"convention or a binding convention."
msgstr ""
msgid "There are these calling conventions:"
msgstr ""
msgid ""
"This is the typical calling convention, where the methods have the type :c:"
"type:`PyCFunction`. The function expects two :c:expr:`PyObject*` values. The "
"first one is the *self* object for methods; for module functions, it is the "
"module object. The second parameter (often called *args*) is a tuple object "
"representing all arguments. This parameter is typically processed using :c:"
"func:`PyArg_ParseTuple` or :c:func:`PyArg_UnpackTuple`."
msgstr ""
msgid ""
"Can only be used in certain combinations with other flags: :ref:"
"`METH_VARARGS | METH_KEYWORDS <METH_VARARGS-METH_KEYWORDS>`, :ref:"
"`METH_FASTCALL | METH_KEYWORDS <METH_FASTCALL-METH_KEYWORDS>` and :ref:"
"`METH_METHOD | METH_FASTCALL | METH_KEYWORDS <METH_METHOD-METH_FASTCALL-"
"METH_KEYWORDS>`."
msgstr ""
msgid ":c:expr:`METH_VARARGS | METH_KEYWORDS`"
msgstr ""
msgid ""
"Methods with these flags must be of type :c:type:`PyCFunctionWithKeywords`. "
"The function expects three parameters: *self*, *args*, *kwargs* where "
"*kwargs* is a dictionary of all the keyword arguments or possibly ``NULL`` "
"if there are no keyword arguments. The parameters are typically processed "
"using :c:func:`PyArg_ParseTupleAndKeywords`."
msgstr ""
msgid ""
"Fast calling convention supporting only positional arguments. The methods "
"have the type :c:type:`PyCFunctionFast`. The first parameter is *self*, the "
"second parameter is a C array of :c:expr:`PyObject*` values indicating the "
"arguments and the third parameter is the number of arguments (the length of "
"the array)."
msgstr ""
msgid "``METH_FASTCALL`` is now part of the :ref:`stable ABI <stable-abi>`."
msgstr ""
msgid ":c:expr:`METH_FASTCALL | METH_KEYWORDS`"
msgstr ""
msgid ""
"Extension of :c:macro:`METH_FASTCALL` supporting also keyword arguments, "
"with methods of type :c:type:`PyCFunctionFastWithKeywords`. Keyword "
"arguments are passed the same way as in the :ref:`vectorcall protocol "
"<vectorcall>`: there is an additional fourth :c:expr:`PyObject*` parameter "
"which is a tuple representing the names of the keyword arguments (which are "
"guaranteed to be strings) or possibly ``NULL`` if there are no keywords. "
"The values of the keyword arguments are stored in the *args* array, after "
"the positional arguments."
msgstr ""
msgid ""
"Can only be used in the combination with other flags: :ref:`METH_METHOD | "
"METH_FASTCALL | METH_KEYWORDS <METH_METHOD-METH_FASTCALL-METH_KEYWORDS>`."
msgstr ""
msgid ":c:expr:`METH_METHOD | METH_FASTCALL | METH_KEYWORDS`"
msgstr ""
msgid ""
"Extension of :ref:`METH_FASTCALL | METH_KEYWORDS <METH_FASTCALL-"
"METH_KEYWORDS>` supporting the *defining class*, that is, the class that "
"contains the method in question. The defining class might be a superclass of "
"``Py_TYPE(self)``."
msgstr ""
msgid ""
"The method needs to be of type :c:type:`PyCMethod`, the same as for "
"``METH_FASTCALL | METH_KEYWORDS`` with ``defining_class`` argument added "
"after ``self``."
msgstr ""
msgid ""
"Methods without parameters don't need to check whether arguments are given "
"if they are listed with the :c:macro:`METH_NOARGS` flag. They need to be of "
"type :c:type:`PyCFunction`. The first parameter is typically named *self* "
"and will hold a reference to the module or object instance. In all cases "
"the second parameter will be ``NULL``."
msgstr ""
msgid ""
"The function must have 2 parameters. Since the second parameter is unused, :"
"c:macro:`Py_UNUSED` can be used to prevent a compiler warning."
msgstr ""
msgid ""
"Methods with a single object argument can be listed with the :c:macro:"
"`METH_O` flag, instead of invoking :c:func:`PyArg_ParseTuple` with a "
"``\"O\"`` argument. They have the type :c:type:`PyCFunction`, with the "
"*self* parameter, and a :c:expr:`PyObject*` parameter representing the "
"single argument."
msgstr ""
msgid ""
"These two constants are not used to indicate the calling convention but the "
"binding when used with methods of classes. These may not be used for "
"functions defined for modules. At most one of these flags may be set for "
"any given method."
msgstr ""
msgid ""
"The method will be passed the type object as the first parameter rather than "
"an instance of the type. This is used to create *class methods*, similar to "
"what is created when using the :func:`classmethod` built-in function."
msgstr ""
"Metodzie zostanie przekazany typ obiektu jako pierwszy parametr zamiast "
"instancji tego typu. Jest to używane aby tworzyć *metody klasowe*, podobnie "
"do tego, co jest tworzone przy użyciu wbudowanej funkcji :func:`classmethod`."
msgid ""
"The method will be passed ``NULL`` as the first parameter rather than an "
"instance of the type. This is used to create *static methods*, similar to "
"what is created when using the :func:`staticmethod` built-in function."
msgstr ""
msgid ""
"One other constant controls whether a method is loaded in place of another "
"definition with the same method name."
msgstr ""
"Jedna pozostała stała kontroluje czy metoda jest ładowana w miejscu innej "
"definicji o tej samej nazwie metody."
msgid ""
"The method will be loaded in place of existing definitions. Without "
"*METH_COEXIST*, the default is to skip repeated definitions. Since slot "
"wrappers are loaded before the method table, the existence of a "
"*sq_contains* slot, for example, would generate a wrapped method named :meth:"
"`~object.__contains__` and preclude the loading of a corresponding "
"PyCFunction with the same name. With the flag defined, the PyCFunction will "
"be loaded in place of the wrapper object and will co-exist with the slot. "
"This is helpful because calls to PyCFunctions are optimized more than "
"wrapper object calls."
msgstr ""
msgid ""
"The type object corresponding to Python C method objects. This is available "
"as :class:`types.BuiltinMethodType` in the Python layer."
msgstr ""
msgid ""
"Return true if *op* is an instance of the :c:type:`PyCMethod_Type` type or a "
"subtype of it. This function always succeeds."
msgstr ""
msgid ""
"This is the same as :c:func:`PyCMethod_Check`, but does not account for "
"subtypes."
msgstr ""
msgid ""
"Turn *ml* into a Python :term:`callable` object. The caller must ensure that "
"*ml* outlives the :term:`callable`. Typically, *ml* is defined as a static "
"variable."
msgstr ""
msgid ""
"The *self* parameter will be passed as the *self* argument to the C function "
"in ``ml->ml_meth`` when invoked. *self* can be ``NULL``."
msgstr ""
msgid ""
"The :term:`callable` object's ``__module__`` attribute can be set from the "
"given *module* argument. *module* should be a Python string, which will be "
"used as name of the module the function is defined in. If unavailable, it "
"can be set to :const:`None` or ``NULL``."
msgstr ""
msgid ":attr:`function.__module__`"
msgstr ":attr:`function.__module__`"
msgid ""
"The *cls* parameter will be passed as the *defining_class* argument to the C "
"function. Must be set if :c:macro:`METH_METHOD` is set on ``ml->ml_flags``."
msgstr ""
msgid ""
"The type object corresponding to Python C function objects. This is "
"available as :class:`types.BuiltinFunctionType` in the Python layer."
msgstr ""
msgid ""
"Return true if *op* is an instance of the :c:type:`PyCFunction_Type` type or "
"a subtype of it. This function always succeeds."
msgstr ""
msgid ""
"This is the same as :c:func:`PyCFunction_Check`, but does not account for "
"subtypes."
msgstr ""
msgid "Equivalent to ``PyCMethod_New(ml, self, module, NULL)``."
msgstr ""
msgid "Equivalent to ``PyCMethod_New(ml, self, NULL, NULL)``."
msgstr ""
msgid ""
"Get the function's flags on *func* as they were passed to :c:member:"
"`~PyMethodDef.ml_flags`."
msgstr ""
msgid ""
"If *func* is not a C function object, this fails with an exception. *func* "
"must not be ``NULL``."
msgstr ""
msgid ""
"This function returns the function's flags on success, and ``-1`` with an "
"exception set on failure."
msgstr ""
msgid ""
"This is the same as :c:func:`PyCFunction_GetFlags`, but without error or "
"type checking."
msgstr ""
msgid ""
"Get the function pointer on *func* as it was passed to :c:member:"
"`~PyMethodDef.ml_meth`."
msgstr ""
msgid ""
"This function returns the function pointer on success, and ``NULL`` with an "
"exception set on failure."
msgstr ""
msgid ""
"This is the same as :c:func:`PyCFunction_GetFunction`, but without error or "
"type checking."
msgstr ""
msgid ""
"Get the \"self\" object on *func*. This is the object that would be passed "
"to the first argument of a :c:type:`PyCFunction`. For C function objects "
"created through a :c:type:`PyMethodDef` on a :c:type:`PyModuleDef`, this is "
"the resulting module object."
msgstr ""
msgid ""
"This function returns a :term:`borrowed reference` to the \"self\" object on "
"success, and ``NULL`` with an exception set on failure."
msgstr ""
msgid ""
"This is the same as :c:func:`PyCFunction_GetSelf`, but without error or type "
"checking."
msgstr ""
msgid "Accessing attributes of extension types"
msgstr ""
msgid ""
"Structure which describes an attribute of a type which corresponds to a C "
"struct member. When defining a class, put a NULL-terminated array of these "
"structures in the :c:member:`~PyTypeObject.tp_members` slot."
msgstr ""
msgid "Its fields are, in order:"
msgstr ""
msgid ""
"Name of the member. A NULL value marks the end of a ``PyMemberDef[]`` array."
msgstr ""
msgid "The string should be static, no copy is made of it."
msgstr ""
msgid ""
"The type of the member in the C struct. See :ref:`PyMemberDef-types` for the "
"possible values."
msgstr ""
msgid ""
"The offset in bytes that the member is located on the type’s object struct."
msgstr ""
msgid ""
"Zero or more of the :ref:`PyMemberDef-flags`, combined using bitwise OR."
msgstr ""
msgid ""
"The docstring, or NULL. The string should be static, no copy is made of it. "
"Typically, it is defined using :c:macro:`PyDoc_STR`."
msgstr ""
msgid ""
"By default (when :c:member:`~PyMemberDef.flags` is ``0``), members allow "
"both read and write access. Use the :c:macro:`Py_READONLY` flag for read-"
"only access. Certain types, like :c:macro:`Py_T_STRING`, imply :c:macro:"
"`Py_READONLY`. Only :c:macro:`Py_T_OBJECT_EX` (and legacy :c:macro:"
"`T_OBJECT`) members can be deleted."
msgstr ""
msgid ""
"For heap-allocated types (created using :c:func:`PyType_FromSpec` or "
"similar), ``PyMemberDef`` may contain a definition for the special member "
"``\"__vectorcalloffset__\"``, corresponding to :c:member:`~PyTypeObject."
"tp_vectorcall_offset` in type objects. This member must be defined with "
"``Py_T_PYSSIZET``, and either ``Py_READONLY`` or ``Py_READONLY | "
"Py_RELATIVE_OFFSET``. For example::"
msgstr ""
msgid ""
"static PyMemberDef spam_type_members[] = {\n"
" {\"__vectorcalloffset__\", Py_T_PYSSIZET,\n"
" offsetof(Spam_object, vectorcall), Py_READONLY},\n"
" {NULL} /* Sentinel */\n"
"};"
msgstr ""
msgid "(You may need to ``#include <stddef.h>`` for :c:func:`!offsetof`.)"
msgstr ""
msgid ""
"The legacy offsets :c:member:`~PyTypeObject.tp_dictoffset` and :c:member:"
"`~PyTypeObject.tp_weaklistoffset` can be defined similarly using "
"``\"__dictoffset__\"`` and ``\"__weaklistoffset__\"`` members, but "
"extensions are strongly encouraged to use :c:macro:`Py_TPFLAGS_MANAGED_DICT` "
"and :c:macro:`Py_TPFLAGS_MANAGED_WEAKREF` instead."
msgstr ""
msgid ""
"``PyMemberDef`` is always available. Previously, it required including "
"``\"structmember.h\"``."
msgstr ""
msgid ""
":c:macro:`Py_RELATIVE_OFFSET` is now allowed for "
"``\"__vectorcalloffset__\"``, ``\"__dictoffset__\"`` and "
"``\"__weaklistoffset__\"``."
msgstr ""
msgid ""
"Get an attribute belonging to the object at address *obj_addr*. The "
"attribute is described by ``PyMemberDef`` *m*. Returns ``NULL`` on error."
msgstr ""
msgid ""
"``PyMember_GetOne`` is always available. Previously, it required including "
"``\"structmember.h\"``."
msgstr ""
msgid ""
"Set an attribute belonging to the object at address *obj_addr* to object "
"*o*. The attribute to set is described by ``PyMemberDef`` *m*. Returns "
"``0`` if successful and a negative value on failure."
msgstr ""
msgid ""
"``PyMember_SetOne`` is always available. Previously, it required including "
"``\"structmember.h\"``."
msgstr ""
msgid "Member flags"
msgstr ""
msgid "The following flags can be used with :c:member:`PyMemberDef.flags`:"
msgstr ""
msgid "Not writable."
msgstr ""
msgid ""
"Emit an ``object.__getattr__`` :ref:`audit event <audit-events>` before "
"reading."
msgstr ""
msgid ""
"Indicates that the :c:member:`~PyMemberDef.offset` of this ``PyMemberDef`` "
"entry indicates an offset from the subclass-specific data, rather than from "
"``PyObject``."
msgstr ""
msgid ""
"Can only be used as part of the :c:data:`Py_tp_members` :c:type:`slot "
"<PyType_Slot>` when creating a class using negative :c:member:`~PyType_Spec."
"basicsize`. It is mandatory in that case. When setting :c:member:"
"`~PyTypeObject.tp_members` from the slot during class creation, Python "
"clears the flag and sets :c:member:`PyMemberDef.offset` to the offset from "
"the ``PyObject`` struct."
msgstr ""
msgid ""
"The :c:macro:`!RESTRICTED`, :c:macro:`!READ_RESTRICTED` and :c:macro:`!"
"WRITE_RESTRICTED` macros available with ``#include \"structmember.h\"`` are "
"deprecated. :c:macro:`!READ_RESTRICTED` and :c:macro:`!RESTRICTED` are "
"equivalent to :c:macro:`Py_AUDIT_READ`; :c:macro:`!WRITE_RESTRICTED` does "
"nothing."
msgstr ""
msgid ""
"The :c:macro:`!READONLY` macro was renamed to :c:macro:`Py_READONLY`. The :c:"
"macro:`!PY_AUDIT_READ` macro was renamed with the ``Py_`` prefix. The new "
"names are now always available. Previously, these required ``#include "
"\"structmember.h\"``. The header is still available and it provides the old "
"names."
msgstr ""
msgid "Member types"
msgstr ""
msgid ""
":c:member:`PyMemberDef.type` can be one of the following macros "
"corresponding to various C types. When the member is accessed in Python, it "
"will be converted to the equivalent Python type. When it is set from Python, "
"it will be converted back to the C type. If that is not possible, an "
"exception such as :exc:`TypeError` or :exc:`ValueError` is raised."
msgstr ""
msgid ""
"Unless marked (D), attributes defined this way cannot be deleted using e.g. :"
"keyword:`del` or :py:func:`delattr`."
msgstr ""
msgid "Macro name"
msgstr ""
msgid "C type"
msgstr ""
msgid "Python type"
msgstr ""
msgid ":c:expr:`char`"
msgstr ":c:expr:`char`"
msgid ":py:class:`int`"
msgstr ":py:class:`int`"
msgid ":c:expr:`short`"
msgstr ":c:expr:`short`"
msgid ":c:expr:`int`"
msgstr ":c:expr:`int`"
msgid ":c:expr:`long`"
msgstr ":c:expr:`long`"
msgid ":c:expr:`long long`"
msgstr ":c:expr:`long long`"
msgid ":c:expr:`unsigned char`"
msgstr ":c:expr:`unsigned char`"
msgid ":c:expr:`unsigned int`"
msgstr ":c:expr:`unsigned int`"
msgid ":c:expr:`unsigned short`"
msgstr ":c:expr:`unsigned short`"
msgid ":c:expr:`unsigned long`"
msgstr ":c:expr:`unsigned long`"
msgid ":c:expr:`unsigned long long`"
msgstr ""
msgid ":c:expr:`Py_ssize_t`"
msgstr ":c:expr:`Py_ssize_t`"
msgid ":c:expr:`float`"
msgstr ":c:expr:`float`"
msgid ":py:class:`float`"
msgstr ":py:class:`float`"
msgid ":c:expr:`double`"
msgstr ":c:expr:`double`"
msgid ":c:expr:`char` (written as 0 or 1)"
msgstr ""
msgid ":py:class:`bool`"
msgstr ":py:class:`bool`"
msgid ":c:expr:`const char *` (*)"
msgstr ""
msgid ":py:class:`str` (RO)"
msgstr ":py:class:`str` (RO)"
msgid ":c:expr:`const char[]` (*)"
msgstr ""
msgid ":c:expr:`char` (0-127)"
msgstr ":c:expr:`char` (0-127)"
msgid ":py:class:`str` (**)"
msgstr ":py:class:`str` (**)"
msgid ":c:expr:`PyObject *`"
msgstr ":c:expr:`PyObject *`"
msgid ":py:class:`object` (D)"
msgstr ":py:class:`object` (D)"
msgid ""
"(*): Zero-terminated, UTF8-encoded C string. With :c:macro:`!Py_T_STRING` "
"the C representation is a pointer; with :c:macro:`!Py_T_STRING_INPLACE` the "
"string is stored directly in the structure."
msgstr ""
msgid "(**): String of length 1. Only ASCII is accepted."
msgstr ""
msgid "(RO): Implies :c:macro:`Py_READONLY`."
msgstr ""
msgid ""
"(D): Can be deleted, in which case the pointer is set to ``NULL``. Reading a "
"``NULL`` pointer raises :py:exc:`AttributeError`."
msgstr ""
msgid ""
"In previous versions, the macros were only available with ``#include "
"\"structmember.h\"`` and were named without the ``Py_`` prefix (e.g. as "
"``T_INT``). The header is still available and contains the old names, along "
"with the following deprecated types:"
msgstr ""
msgid ""
"Like ``Py_T_OBJECT_EX``, but ``NULL`` is converted to ``None``. This results "
"in surprising behavior in Python: deleting the attribute effectively sets it "
"to ``None``."
msgstr ""
msgid "Always ``None``. Must be used with :c:macro:`Py_READONLY`."
msgstr ""
msgid "Defining Getters and Setters"
msgstr ""
msgid ""
"Structure to define property-like access for a type. See also description of "
"the :c:member:`PyTypeObject.tp_getset` slot."
msgstr ""
msgid "attribute name"
msgstr ""
msgid "C function to get the attribute."
msgstr ""
msgid ""
"Optional C function to set or delete the attribute. If ``NULL``, the "
"attribute is read-only."
msgstr ""
msgid "optional docstring"
msgstr ""
msgid ""
"Optional user data pointer, providing additional data for getter and setter."
msgstr ""
msgid ""
"The ``get`` function takes one :c:expr:`PyObject*` parameter (the instance) "
"and a user data pointer (the associated ``closure``):"
msgstr ""
msgid ""
"It should return a new reference on success or ``NULL`` with a set exception "
"on failure."
msgstr ""
msgid ""
"``set`` functions take two :c:expr:`PyObject*` parameters (the instance and "
"the value to be set) and a user data pointer (the associated ``closure``):"
msgstr ""
msgid ""
"In case the attribute should be deleted the second parameter is ``NULL``. "
"Should return ``0`` on success or ``-1`` with a set exception on failure."
msgstr ""
msgid "built-in function"
msgstr "funkcja wbudowana"
msgid "classmethod"
msgstr ""
msgid "staticmethod"
msgstr ""
msgid "READ_RESTRICTED (C macro)"
msgstr ""
msgid "WRITE_RESTRICTED (C macro)"
msgstr ""
msgid "RESTRICTED (C macro)"
msgstr ""
msgid "READONLY (C macro)"
msgstr ""
msgid "T_BYTE (C macro)"
msgstr ""
msgid "T_SHORT (C macro)"
msgstr ""
msgid "T_INT (C macro)"
msgstr ""
msgid "T_LONG (C macro)"
msgstr ""
msgid "T_LONGLONG (C macro)"
msgstr ""
msgid "T_UBYTE (C macro)"
msgstr ""
msgid "T_USHORT (C macro)"
msgstr ""
msgid "T_UINT (C macro)"
msgstr ""
msgid "T_ULONG (C macro)"
msgstr ""
msgid "T_ULONGULONG (C macro)"
msgstr ""
msgid "T_PYSSIZET (C macro)"
msgstr ""
You can’t perform that action at this time.