-
-
Notifications
You must be signed in to change notification settings - Fork 40
Expand file tree
/
Copy pathnewtypes.po
More file actions
992 lines (875 loc) · 33.3 KB
/
newtypes.po
File metadata and controls
992 lines (875 loc) · 33.3 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
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2025, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Rafael Fontenelle <rffontenelle@gmail.com>, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.12\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-01-03 14:53+0000\n"
"PO-Revision-Date: 2025-07-18 19:57+0000\n"
"Last-Translator: Rafael Fontenelle <rffontenelle@gmail.com>, 2025\n"
"Language-Team: Portuguese (Brazil) (https://app.transifex.com/python-doc/"
"teams/5390/pt_BR/)\n"
"Language: pt_BR\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=3; plural=(n == 0 || n == 1) ? 0 : n != 0 && n % "
"1000000 == 0 ? 1 : 2;\n"
#: ../../extending/newtypes.rst:7
msgid "Defining Extension Types: Assorted Topics"
msgstr ""
#: ../../extending/newtypes.rst:11
msgid ""
"This section aims to give a quick fly-by on the various type methods you can "
"implement and what they do."
msgstr ""
#: ../../extending/newtypes.rst:14
msgid ""
"Here is the definition of :c:type:`PyTypeObject`, with some fields only used "
"in :ref:`debug builds <debug-build>` omitted:"
msgstr ""
#: ../../extending/newtypes.rst:17
msgid ""
"typedef struct _typeobject {\n"
" PyObject_VAR_HEAD\n"
" const char *tp_name; /* For printing, in format \"<module>.<name>\" */\n"
" Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */\n"
"\n"
" /* Methods to implement standard operations */\n"
"\n"
" destructor tp_dealloc;\n"
" Py_ssize_t tp_vectorcall_offset;\n"
" getattrfunc tp_getattr;\n"
" setattrfunc tp_setattr;\n"
" PyAsyncMethods *tp_as_async; /* formerly known as tp_compare (Python 2)\n"
" or tp_reserved (Python 3) */\n"
" reprfunc tp_repr;\n"
"\n"
" /* Method suites for standard classes */\n"
"\n"
" PyNumberMethods *tp_as_number;\n"
" PySequenceMethods *tp_as_sequence;\n"
" PyMappingMethods *tp_as_mapping;\n"
"\n"
" /* More standard operations (here for binary compatibility) */\n"
"\n"
" hashfunc tp_hash;\n"
" ternaryfunc tp_call;\n"
" reprfunc tp_str;\n"
" getattrofunc tp_getattro;\n"
" setattrofunc tp_setattro;\n"
"\n"
" /* Functions to access object as input/output buffer */\n"
" PyBufferProcs *tp_as_buffer;\n"
"\n"
" /* Flags to define presence of optional/expanded features */\n"
" unsigned long tp_flags;\n"
"\n"
" const char *tp_doc; /* Documentation string */\n"
"\n"
" /* Assigned meaning in release 2.0 */\n"
" /* call function for all accessible objects */\n"
" traverseproc tp_traverse;\n"
"\n"
" /* delete references to contained objects */\n"
" inquiry tp_clear;\n"
"\n"
" /* Assigned meaning in release 2.1 */\n"
" /* rich comparisons */\n"
" richcmpfunc tp_richcompare;\n"
"\n"
" /* weak reference enabler */\n"
" Py_ssize_t tp_weaklistoffset;\n"
"\n"
" /* Iterators */\n"
" getiterfunc tp_iter;\n"
" iternextfunc tp_iternext;\n"
"\n"
" /* Attribute descriptor and subclassing stuff */\n"
" struct PyMethodDef *tp_methods;\n"
" struct PyMemberDef *tp_members;\n"
" struct PyGetSetDef *tp_getset;\n"
" // Strong reference on a heap type, borrowed reference on a static type\n"
" struct _typeobject *tp_base;\n"
" PyObject *tp_dict;\n"
" descrgetfunc tp_descr_get;\n"
" descrsetfunc tp_descr_set;\n"
" Py_ssize_t tp_dictoffset;\n"
" initproc tp_init;\n"
" allocfunc tp_alloc;\n"
" newfunc tp_new;\n"
" freefunc tp_free; /* Low-level free-memory routine */\n"
" inquiry tp_is_gc; /* For PyObject_IS_GC */\n"
" PyObject *tp_bases;\n"
" PyObject *tp_mro; /* method resolution order */\n"
" PyObject *tp_cache;\n"
" PyObject *tp_subclasses;\n"
" PyObject *tp_weaklist;\n"
" destructor tp_del;\n"
"\n"
" /* Type attribute cache version tag. Added in version 2.6 */\n"
" unsigned int tp_version_tag;\n"
"\n"
" destructor tp_finalize;\n"
" vectorcallfunc tp_vectorcall;\n"
"\n"
" /* bitset of which type-watchers care about this type */\n"
" unsigned char tp_watched;\n"
"} PyTypeObject;\n"
msgstr ""
#: ../../extending/newtypes.rst:20
msgid ""
"Now that's a *lot* of methods. Don't worry too much though -- if you have a "
"type you want to define, the chances are very good that you will only "
"implement a handful of these."
msgstr ""
#: ../../extending/newtypes.rst:24
msgid ""
"As you probably expect by now, we're going to go over this and give more "
"information about the various handlers. We won't go in the order they are "
"defined in the structure, because there is a lot of historical baggage that "
"impacts the ordering of the fields. It's often easiest to find an example "
"that includes the fields you need and then change the values to suit your "
"new type. ::"
msgstr ""
#: ../../extending/newtypes.rst:31
msgid "const char *tp_name; /* For printing */"
msgstr ""
#: ../../extending/newtypes.rst:33
msgid ""
"The name of the type -- as mentioned in the previous chapter, this will "
"appear in various places, almost entirely for diagnostic purposes. Try to "
"choose something that will be helpful in such a situation! ::"
msgstr ""
#: ../../extending/newtypes.rst:37
msgid "Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */"
msgstr ""
#: ../../extending/newtypes.rst:39
msgid ""
"These fields tell the runtime how much memory to allocate when new objects "
"of this type are created. Python has some built-in support for variable "
"length structures (think: strings, tuples) which is where the :c:member:"
"`~PyTypeObject.tp_itemsize` field comes in. This will be dealt with "
"later. ::"
msgstr ""
#: ../../extending/newtypes.rst:44
msgid "const char *tp_doc;"
msgstr ""
#: ../../extending/newtypes.rst:46
msgid ""
"Here you can put a string (or its address) that you want returned when the "
"Python script references ``obj.__doc__`` to retrieve the doc string."
msgstr ""
#: ../../extending/newtypes.rst:49
msgid ""
"Now we come to the basic type methods -- the ones most extension types will "
"implement."
msgstr ""
#: ../../extending/newtypes.rst:54
msgid "Finalization and De-allocation"
msgstr ""
#: ../../extending/newtypes.rst:64
msgid "destructor tp_dealloc;"
msgstr ""
#: ../../extending/newtypes.rst:66
msgid ""
"This function is called when the reference count of the instance of your "
"type is reduced to zero and the Python interpreter wants to reclaim it. If "
"your type has memory to free or other clean-up to perform, you can put it "
"here. The object itself needs to be freed here as well. Here is an example "
"of this function::"
msgstr ""
#: ../../extending/newtypes.rst:72
msgid ""
"static void\n"
"newdatatype_dealloc(newdatatypeobject *obj)\n"
"{\n"
" free(obj->obj_UnderlyingDatatypePtr);\n"
" Py_TYPE(obj)->tp_free((PyObject *)obj);\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:79
msgid ""
"If your type supports garbage collection, the destructor should call :c:func:"
"`PyObject_GC_UnTrack` before clearing any member fields::"
msgstr ""
#: ../../extending/newtypes.rst:82
msgid ""
"static void\n"
"newdatatype_dealloc(newdatatypeobject *obj)\n"
"{\n"
" PyObject_GC_UnTrack(obj);\n"
" Py_CLEAR(obj->other_obj);\n"
" ...\n"
" Py_TYPE(obj)->tp_free((PyObject *)obj);\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:95
msgid ""
"One important requirement of the deallocator function is that it leaves any "
"pending exceptions alone. This is important since deallocators are "
"frequently called as the interpreter unwinds the Python stack; when the "
"stack is unwound due to an exception (rather than normal returns), nothing "
"is done to protect the deallocators from seeing that an exception has "
"already been set. Any actions which a deallocator performs which may cause "
"additional Python code to be executed may detect that an exception has been "
"set. This can lead to misleading errors from the interpreter. The proper "
"way to protect against this is to save a pending exception before performing "
"the unsafe action, and restoring it when done. This can be done using the :"
"c:func:`PyErr_Fetch` and :c:func:`PyErr_Restore` functions::"
msgstr ""
#: ../../extending/newtypes.rst:107
msgid ""
"static void\n"
"my_dealloc(PyObject *obj)\n"
"{\n"
" MyObject *self = (MyObject *) obj;\n"
" PyObject *cbresult;\n"
"\n"
" if (self->my_callback != NULL) {\n"
" PyObject *err_type, *err_value, *err_traceback;\n"
"\n"
" /* This saves the current exception state */\n"
" PyErr_Fetch(&err_type, &err_value, &err_traceback);\n"
"\n"
" cbresult = PyObject_CallNoArgs(self->my_callback);\n"
" if (cbresult == NULL)\n"
" PyErr_WriteUnraisable(self->my_callback);\n"
" else\n"
" Py_DECREF(cbresult);\n"
"\n"
" /* This restores the saved exception state */\n"
" PyErr_Restore(err_type, err_value, err_traceback);\n"
"\n"
" Py_DECREF(self->my_callback);\n"
" }\n"
" Py_TYPE(obj)->tp_free((PyObject*)self);\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:134
msgid ""
"There are limitations to what you can safely do in a deallocator function. "
"First, if your type supports garbage collection (using :c:member:"
"`~PyTypeObject.tp_traverse` and/or :c:member:`~PyTypeObject.tp_clear`), some "
"of the object's members can have been cleared or finalized by the time :c:"
"member:`~PyTypeObject.tp_dealloc` is called. Second, in :c:member:"
"`~PyTypeObject.tp_dealloc`, your object is in an unstable state: its "
"reference count is equal to zero. Any call to a non-trivial object or API "
"(as in the example above) might end up calling :c:member:`~PyTypeObject."
"tp_dealloc` again, causing a double free and a crash."
msgstr ""
#: ../../extending/newtypes.rst:143
msgid ""
"Starting with Python 3.4, it is recommended not to put any complex "
"finalization code in :c:member:`~PyTypeObject.tp_dealloc`, and instead use "
"the new :c:member:`~PyTypeObject.tp_finalize` type method."
msgstr ""
#: ../../extending/newtypes.rst:148
msgid ":pep:`442` explains the new finalization scheme."
msgstr ""
#: ../../extending/newtypes.rst:155
msgid "Object Presentation"
msgstr ""
#: ../../extending/newtypes.rst:157
msgid ""
"In Python, there are two ways to generate a textual representation of an "
"object: the :func:`repr` function, and the :func:`str` function. (The :func:"
"`print` function just calls :func:`str`.) These handlers are both optional."
msgstr ""
#: ../../extending/newtypes.rst:163
msgid ""
"reprfunc tp_repr;\n"
"reprfunc tp_str;"
msgstr ""
#: ../../extending/newtypes.rst:166
msgid ""
"The :c:member:`~PyTypeObject.tp_repr` handler should return a string object "
"containing a representation of the instance for which it is called. Here is "
"a simple example::"
msgstr ""
#: ../../extending/newtypes.rst:170
msgid ""
"static PyObject *\n"
"newdatatype_repr(newdatatypeobject *obj)\n"
"{\n"
" return PyUnicode_FromFormat(\"Repr-ified_newdatatype{{size:%d}}\",\n"
" obj->obj_UnderlyingDatatypePtr->size);\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:177
msgid ""
"If no :c:member:`~PyTypeObject.tp_repr` handler is specified, the "
"interpreter will supply a representation that uses the type's :c:member:"
"`~PyTypeObject.tp_name` and a uniquely identifying value for the object."
msgstr ""
#: ../../extending/newtypes.rst:181
msgid ""
"The :c:member:`~PyTypeObject.tp_str` handler is to :func:`str` what the :c:"
"member:`~PyTypeObject.tp_repr` handler described above is to :func:`repr`; "
"that is, it is called when Python code calls :func:`str` on an instance of "
"your object. Its implementation is very similar to the :c:member:"
"`~PyTypeObject.tp_repr` function, but the resulting string is intended for "
"human consumption. If :c:member:`~PyTypeObject.tp_str` is not specified, "
"the :c:member:`~PyTypeObject.tp_repr` handler is used instead."
msgstr ""
#: ../../extending/newtypes.rst:188
msgid "Here is a simple example::"
msgstr ""
#: ../../extending/newtypes.rst:190
msgid ""
"static PyObject *\n"
"newdatatype_str(newdatatypeobject *obj)\n"
"{\n"
" return PyUnicode_FromFormat(\"Stringified_newdatatype{{size:%d}}\",\n"
" obj->obj_UnderlyingDatatypePtr->size);\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:200
msgid "Attribute Management"
msgstr ""
#: ../../extending/newtypes.rst:202
msgid ""
"For every object which can support attributes, the corresponding type must "
"provide the functions that control how the attributes are resolved. There "
"needs to be a function which can retrieve attributes (if any are defined), "
"and another to set attributes (if setting attributes is allowed). Removing "
"an attribute is a special case, for which the new value passed to the "
"handler is ``NULL``."
msgstr ""
#: ../../extending/newtypes.rst:208
msgid ""
"Python supports two pairs of attribute handlers; a type that supports "
"attributes only needs to implement the functions for one pair. The "
"difference is that one pair takes the name of the attribute as a :c:expr:"
"`char\\*`, while the other accepts a :c:expr:`PyObject*`. Each type can use "
"whichever pair makes more sense for the implementation's convenience. ::"
msgstr ""
#: ../../extending/newtypes.rst:214
msgid ""
"getattrfunc tp_getattr; /* char * version */\n"
"setattrfunc tp_setattr;\n"
"/* ... */\n"
"getattrofunc tp_getattro; /* PyObject * version */\n"
"setattrofunc tp_setattro;"
msgstr ""
#: ../../extending/newtypes.rst:220
msgid ""
"If accessing attributes of an object is always a simple operation (this will "
"be explained shortly), there are generic implementations which can be used "
"to provide the :c:expr:`PyObject*` version of the attribute management "
"functions. The actual need for type-specific attribute handlers almost "
"completely disappeared starting with Python 2.2, though there are many "
"examples which have not been updated to use some of the new generic "
"mechanism that is available."
msgstr ""
#: ../../extending/newtypes.rst:231
msgid "Generic Attribute Management"
msgstr ""
#: ../../extending/newtypes.rst:233
msgid ""
"Most extension types only use *simple* attributes. So, what makes the "
"attributes simple? There are only a couple of conditions that must be met:"
msgstr ""
#: ../../extending/newtypes.rst:236
msgid ""
"The name of the attributes must be known when :c:func:`PyType_Ready` is "
"called."
msgstr ""
#: ../../extending/newtypes.rst:239
msgid ""
"No special processing is needed to record that an attribute was looked up or "
"set, nor do actions need to be taken based on the value."
msgstr ""
#: ../../extending/newtypes.rst:242
msgid ""
"Note that this list does not place any restrictions on the values of the "
"attributes, when the values are computed, or how relevant data is stored."
msgstr ""
#: ../../extending/newtypes.rst:245
msgid ""
"When :c:func:`PyType_Ready` is called, it uses three tables referenced by "
"the type object to create :term:`descriptor`\\s which are placed in the "
"dictionary of the type object. Each descriptor controls access to one "
"attribute of the instance object. Each of the tables is optional; if all "
"three are ``NULL``, instances of the type will only have attributes that are "
"inherited from their base type, and should leave the :c:member:"
"`~PyTypeObject.tp_getattro` and :c:member:`~PyTypeObject.tp_setattro` fields "
"``NULL`` as well, allowing the base type to handle attributes."
msgstr ""
#: ../../extending/newtypes.rst:253
msgid "The tables are declared as three fields of the type object::"
msgstr ""
#: ../../extending/newtypes.rst:255
msgid ""
"struct PyMethodDef *tp_methods;\n"
"struct PyMemberDef *tp_members;\n"
"struct PyGetSetDef *tp_getset;"
msgstr ""
#: ../../extending/newtypes.rst:259
msgid ""
"If :c:member:`~PyTypeObject.tp_methods` is not ``NULL``, it must refer to an "
"array of :c:type:`PyMethodDef` structures. Each entry in the table is an "
"instance of this structure::"
msgstr ""
#: ../../extending/newtypes.rst:263
msgid ""
"typedef struct PyMethodDef {\n"
" const char *ml_name; /* method name */\n"
" PyCFunction ml_meth; /* implementation function */\n"
" int ml_flags; /* flags */\n"
" const char *ml_doc; /* docstring */\n"
"} PyMethodDef;"
msgstr ""
#: ../../extending/newtypes.rst:270
msgid ""
"One entry should be defined for each method provided by the type; no entries "
"are needed for methods inherited from a base type. One additional entry is "
"needed at the end; it is a sentinel that marks the end of the array. The :c:"
"member:`~PyMethodDef.ml_name` field of the sentinel must be ``NULL``."
msgstr ""
#: ../../extending/newtypes.rst:275
msgid ""
"The second table is used to define attributes which map directly to data "
"stored in the instance. A variety of primitive C types are supported, and "
"access may be read-only or read-write. The structures in the table are "
"defined as::"
msgstr ""
#: ../../extending/newtypes.rst:279
msgid ""
"typedef struct PyMemberDef {\n"
" const char *name;\n"
" int type;\n"
" int offset;\n"
" int flags;\n"
" const char *doc;\n"
"} PyMemberDef;"
msgstr ""
#: ../../extending/newtypes.rst:287
msgid ""
"For each entry in the table, a :term:`descriptor` will be constructed and "
"added to the type which will be able to extract a value from the instance "
"structure. The :c:member:`~PyMemberDef.type` field should contain a type "
"code like :c:macro:`Py_T_INT` or :c:macro:`Py_T_DOUBLE`; the value will be "
"used to determine how to convert Python values to and from C values. The :c:"
"member:`~PyMemberDef.flags` field is used to store flags which control how "
"the attribute can be accessed: you can set it to :c:macro:`Py_READONLY` to "
"prevent Python code from setting it."
msgstr ""
#: ../../extending/newtypes.rst:295
msgid ""
"An interesting advantage of using the :c:member:`~PyTypeObject.tp_members` "
"table to build descriptors that are used at runtime is that any attribute "
"defined this way can have an associated doc string simply by providing the "
"text in the table. An application can use the introspection API to retrieve "
"the descriptor from the class object, and get the doc string using its :attr:"
"`~type.__doc__` attribute."
msgstr ""
#: ../../extending/newtypes.rst:301
msgid ""
"As with the :c:member:`~PyTypeObject.tp_methods` table, a sentinel entry "
"with a :c:member:`~PyMethodDef.ml_name` value of ``NULL`` is required."
msgstr ""
#: ../../extending/newtypes.rst:315
msgid "Type-specific Attribute Management"
msgstr ""
#: ../../extending/newtypes.rst:317
msgid ""
"For simplicity, only the :c:expr:`char\\*` version will be demonstrated "
"here; the type of the name parameter is the only difference between the :c:"
"expr:`char\\*` and :c:expr:`PyObject*` flavors of the interface. This "
"example effectively does the same thing as the generic example above, but "
"does not use the generic support added in Python 2.2. It explains how the "
"handler functions are called, so that if you do need to extend their "
"functionality, you'll understand what needs to be done."
msgstr ""
#: ../../extending/newtypes.rst:325
msgid ""
"The :c:member:`~PyTypeObject.tp_getattr` handler is called when the object "
"requires an attribute look-up. It is called in the same situations where "
"the :meth:`~object.__getattr__` method of a class would be called."
msgstr ""
#: ../../extending/newtypes.rst:329
msgid "Here is an example::"
msgstr "Aqui está um exemplo::"
#: ../../extending/newtypes.rst:331
msgid ""
"static PyObject *\n"
"newdatatype_getattr(newdatatypeobject *obj, char *name)\n"
"{\n"
" if (strcmp(name, \"data\") == 0)\n"
" {\n"
" return PyLong_FromLong(obj->data);\n"
" }\n"
"\n"
" PyErr_Format(PyExc_AttributeError,\n"
" \"'%.100s' object has no attribute '%.400s'\",\n"
" Py_TYPE(obj)->tp_name, name);\n"
" return NULL;\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:345
msgid ""
"The :c:member:`~PyTypeObject.tp_setattr` handler is called when the :meth:"
"`~object.__setattr__` or :meth:`~object.__delattr__` method of a class "
"instance would be called. When an attribute should be deleted, the third "
"parameter will be ``NULL``. Here is an example that simply raises an "
"exception; if this were really all you wanted, the :c:member:`~PyTypeObject."
"tp_setattr` handler should be set to ``NULL``. ::"
msgstr ""
#: ../../extending/newtypes.rst:351
msgid ""
"static int\n"
"newdatatype_setattr(newdatatypeobject *obj, char *name, PyObject *v)\n"
"{\n"
" PyErr_Format(PyExc_RuntimeError, \"Read-only attribute: %s\", name);\n"
" return -1;\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:359
msgid "Object Comparison"
msgstr ""
#: ../../extending/newtypes.rst:363
msgid "richcmpfunc tp_richcompare;"
msgstr ""
#: ../../extending/newtypes.rst:365
msgid ""
"The :c:member:`~PyTypeObject.tp_richcompare` handler is called when "
"comparisons are needed. It is analogous to the :ref:`rich comparison "
"methods <richcmpfuncs>`, like :meth:`!__lt__`, and also called by :c:func:"
"`PyObject_RichCompare` and :c:func:`PyObject_RichCompareBool`."
msgstr ""
#: ../../extending/newtypes.rst:370
msgid ""
"This function is called with two Python objects and the operator as "
"arguments, where the operator is one of ``Py_EQ``, ``Py_NE``, ``Py_LE``, "
"``Py_GE``, ``Py_LT`` or ``Py_GT``. It should compare the two objects with "
"respect to the specified operator and return ``Py_True`` or ``Py_False`` if "
"the comparison is successful, ``Py_NotImplemented`` to indicate that "
"comparison is not implemented and the other object's comparison method "
"should be tried, or ``NULL`` if an exception was set."
msgstr ""
#: ../../extending/newtypes.rst:378
msgid ""
"Here is a sample implementation, for a datatype that is considered equal if "
"the size of an internal pointer is equal::"
msgstr ""
#: ../../extending/newtypes.rst:381
msgid ""
"static PyObject *\n"
"newdatatype_richcmp(newdatatypeobject *obj1, newdatatypeobject *obj2, int "
"op)\n"
"{\n"
" PyObject *result;\n"
" int c, size1, size2;\n"
"\n"
" /* code to make sure that both arguments are of type\n"
" newdatatype omitted */\n"
"\n"
" size1 = obj1->obj_UnderlyingDatatypePtr->size;\n"
" size2 = obj2->obj_UnderlyingDatatypePtr->size;\n"
"\n"
" switch (op) {\n"
" case Py_LT: c = size1 < size2; break;\n"
" case Py_LE: c = size1 <= size2; break;\n"
" case Py_EQ: c = size1 == size2; break;\n"
" case Py_NE: c = size1 != size2; break;\n"
" case Py_GT: c = size1 > size2; break;\n"
" case Py_GE: c = size1 >= size2; break;\n"
" }\n"
" result = c ? Py_True : Py_False;\n"
" Py_INCREF(result);\n"
" return result;\n"
" }"
msgstr ""
#: ../../extending/newtypes.rst:408
msgid "Abstract Protocol Support"
msgstr ""
#: ../../extending/newtypes.rst:410
msgid ""
"Python supports a variety of *abstract* 'protocols;' the specific interfaces "
"provided to use these interfaces are documented in :ref:`abstract`."
msgstr ""
#: ../../extending/newtypes.rst:414
msgid ""
"A number of these abstract interfaces were defined early in the development "
"of the Python implementation. In particular, the number, mapping, and "
"sequence protocols have been part of Python since the beginning. Other "
"protocols have been added over time. For protocols which depend on several "
"handler routines from the type implementation, the older protocols have been "
"defined as optional blocks of handlers referenced by the type object. For "
"newer protocols there are additional slots in the main type object, with a "
"flag bit being set to indicate that the slots are present and should be "
"checked by the interpreter. (The flag bit does not indicate that the slot "
"values are non-``NULL``. The flag may be set to indicate the presence of a "
"slot, but a slot may still be unfilled.) ::"
msgstr ""
#: ../../extending/newtypes.rst:425
msgid ""
"PyNumberMethods *tp_as_number;\n"
"PySequenceMethods *tp_as_sequence;\n"
"PyMappingMethods *tp_as_mapping;"
msgstr ""
#: ../../extending/newtypes.rst:429
msgid ""
"If you wish your object to be able to act like a number, a sequence, or a "
"mapping object, then you place the address of a structure that implements "
"the C type :c:type:`PyNumberMethods`, :c:type:`PySequenceMethods`, or :c:"
"type:`PyMappingMethods`, respectively. It is up to you to fill in this "
"structure with appropriate values. You can find examples of the use of each "
"of these in the :file:`Objects` directory of the Python source "
"distribution. ::"
msgstr ""
#: ../../extending/newtypes.rst:436
msgid "hashfunc tp_hash;"
msgstr ""
#: ../../extending/newtypes.rst:438
msgid ""
"This function, if you choose to provide it, should return a hash number for "
"an instance of your data type. Here is a simple example::"
msgstr ""
#: ../../extending/newtypes.rst:441
msgid ""
"static Py_hash_t\n"
"newdatatype_hash(newdatatypeobject *obj)\n"
"{\n"
" Py_hash_t result;\n"
" result = obj->some_size + 32767 * obj->some_number;\n"
" if (result == -1)\n"
" result = -2;\n"
" return result;\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:451
msgid ""
":c:type:`!Py_hash_t` is a signed integer type with a platform-varying width. "
"Returning ``-1`` from :c:member:`~PyTypeObject.tp_hash` indicates an error, "
"which is why you should be careful to avoid returning it when hash "
"computation is successful, as seen above."
msgstr ""
#: ../../extending/newtypes.rst:458
msgid "ternaryfunc tp_call;"
msgstr ""
#: ../../extending/newtypes.rst:460
msgid ""
"This function is called when an instance of your data type is \"called\", "
"for example, if ``obj1`` is an instance of your data type and the Python "
"script contains ``obj1('hello')``, the :c:member:`~PyTypeObject.tp_call` "
"handler is invoked."
msgstr ""
#: ../../extending/newtypes.rst:464
msgid "This function takes three arguments:"
msgstr ""
#: ../../extending/newtypes.rst:466
msgid ""
"*self* is the instance of the data type which is the subject of the call. If "
"the call is ``obj1('hello')``, then *self* is ``obj1``."
msgstr ""
#: ../../extending/newtypes.rst:469
msgid ""
"*args* is a tuple containing the arguments to the call. You can use :c:func:"
"`PyArg_ParseTuple` to extract the arguments."
msgstr ""
#: ../../extending/newtypes.rst:472
msgid ""
"*kwds* is a dictionary of keyword arguments that were passed. If this is non-"
"``NULL`` and you support keyword arguments, use :c:func:"
"`PyArg_ParseTupleAndKeywords` to extract the arguments. If you do not want "
"to support keyword arguments and this is non-``NULL``, raise a :exc:"
"`TypeError` with a message saying that keyword arguments are not supported."
msgstr ""
#: ../../extending/newtypes.rst:478
msgid "Here is a toy ``tp_call`` implementation::"
msgstr ""
#: ../../extending/newtypes.rst:480
msgid ""
"static PyObject *\n"
"newdatatype_call(newdatatypeobject *obj, PyObject *args, PyObject *kwds)\n"
"{\n"
" PyObject *result;\n"
" const char *arg1;\n"
" const char *arg2;\n"
" const char *arg3;\n"
"\n"
" if (!PyArg_ParseTuple(args, \"sss:call\", &arg1, &arg2, &arg3)) {\n"
" return NULL;\n"
" }\n"
" result = PyUnicode_FromFormat(\n"
" \"Returning -- value: [%d] arg1: [%s] arg2: [%s] arg3: [%s]\\n\",\n"
" obj->obj_UnderlyingDatatypePtr->size,\n"
" arg1, arg2, arg3);\n"
" return result;\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:500
msgid ""
"/* Iterators */\n"
"getiterfunc tp_iter;\n"
"iternextfunc tp_iternext;"
msgstr ""
#: ../../extending/newtypes.rst:504
msgid ""
"These functions provide support for the iterator protocol. Both handlers "
"take exactly one parameter, the instance for which they are being called, "
"and return a new reference. In the case of an error, they should set an "
"exception and return ``NULL``. :c:member:`~PyTypeObject.tp_iter` "
"corresponds to the Python :meth:`~object.__iter__` method, while :c:member:"
"`~PyTypeObject.tp_iternext` corresponds to the Python :meth:`~iterator."
"__next__` method."
msgstr ""
#: ../../extending/newtypes.rst:511
msgid ""
"Any :term:`iterable` object must implement the :c:member:`~PyTypeObject."
"tp_iter` handler, which must return an :term:`iterator` object. Here the "
"same guidelines apply as for Python classes:"
msgstr ""
#: ../../extending/newtypes.rst:515
msgid ""
"For collections (such as lists and tuples) which can support multiple "
"independent iterators, a new iterator should be created and returned by each "
"call to :c:member:`~PyTypeObject.tp_iter`."
msgstr ""
#: ../../extending/newtypes.rst:518
msgid ""
"Objects which can only be iterated over once (usually due to side effects of "
"iteration, such as file objects) can implement :c:member:`~PyTypeObject."
"tp_iter` by returning a new reference to themselves -- and should also "
"therefore implement the :c:member:`~PyTypeObject.tp_iternext` handler."
msgstr ""
#: ../../extending/newtypes.rst:523
msgid ""
"Any :term:`iterator` object should implement both :c:member:`~PyTypeObject."
"tp_iter` and :c:member:`~PyTypeObject.tp_iternext`. An iterator's :c:member:"
"`~PyTypeObject.tp_iter` handler should return a new reference to the "
"iterator. Its :c:member:`~PyTypeObject.tp_iternext` handler should return a "
"new reference to the next object in the iteration, if there is one. If the "
"iteration has reached the end, :c:member:`~PyTypeObject.tp_iternext` may "
"return ``NULL`` without setting an exception, or it may set :exc:"
"`StopIteration` *in addition* to returning ``NULL``; avoiding the exception "
"can yield slightly better performance. If an actual error occurs, :c:member:"
"`~PyTypeObject.tp_iternext` should always set an exception and return "
"``NULL``."
msgstr ""
#: ../../extending/newtypes.rst:539
msgid "Weak Reference Support"
msgstr ""
#: ../../extending/newtypes.rst:541
msgid ""
"One of the goals of Python's weak reference implementation is to allow any "
"type to participate in the weak reference mechanism without incurring the "
"overhead on performance-critical objects (such as numbers)."
msgstr ""
#: ../../extending/newtypes.rst:546
msgid "Documentation for the :mod:`weakref` module."
msgstr "Documentação do módulo :mod:`weakref`."
#: ../../extending/newtypes.rst:548
msgid ""
"For an object to be weakly referenceable, the extension type must set the "
"``Py_TPFLAGS_MANAGED_WEAKREF`` bit of the :c:member:`~PyTypeObject.tp_flags` "
"field. The legacy :c:member:`~PyTypeObject.tp_weaklistoffset` field should "
"be left as zero."
msgstr ""
#: ../../extending/newtypes.rst:553
msgid ""
"Concretely, here is how the statically declared type object would look::"
msgstr ""
#: ../../extending/newtypes.rst:555
msgid ""
"static PyTypeObject TrivialType = {\n"
" PyVarObject_HEAD_INIT(NULL, 0)\n"
" /* ... other members omitted for brevity ... */\n"
" .tp_flags = Py_TPFLAGS_MANAGED_WEAKREF | ...,\n"
"};"
msgstr ""
#: ../../extending/newtypes.rst:562
msgid ""
"The only further addition is that ``tp_dealloc`` needs to clear any weak "
"references (by calling :c:func:`PyObject_ClearWeakRefs`)::"
msgstr ""
#: ../../extending/newtypes.rst:565
msgid ""
"static void\n"
"Trivial_dealloc(TrivialObject *self)\n"
"{\n"
" /* Clear weakrefs first before calling any destructors */\n"
" PyObject_ClearWeakRefs((PyObject *) self);\n"
" /* ... remainder of destruction code omitted for brevity ... */\n"
" Py_TYPE(self)->tp_free((PyObject *) self);\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:576
msgid "More Suggestions"
msgstr ""
#: ../../extending/newtypes.rst:578
msgid ""
"In order to learn how to implement any specific method for your new data "
"type, get the :term:`CPython` source code. Go to the :file:`Objects` "
"directory, then search the C source files for ``tp_`` plus the function you "
"want (for example, ``tp_richcompare``). You will find examples of the "
"function you want to implement."
msgstr ""
#: ../../extending/newtypes.rst:584
msgid ""
"When you need to verify that an object is a concrete instance of the type "
"you are implementing, use the :c:func:`PyObject_TypeCheck` function. A "
"sample of its use might be something like the following::"
msgstr ""
#: ../../extending/newtypes.rst:588
msgid ""
"if (!PyObject_TypeCheck(some_object, &MyType)) {\n"
" PyErr_SetString(PyExc_TypeError, \"arg #1 not a mything\");\n"
" return NULL;\n"
"}"
msgstr ""
#: ../../extending/newtypes.rst:594
msgid "Download CPython source releases."
msgstr ""
#: ../../extending/newtypes.rst:595
msgid "https://www.python.org/downloads/source/"
msgstr "https://www.python.org/downloads/source/"
#: ../../extending/newtypes.rst:597
msgid ""
"The CPython project on GitHub, where the CPython source code is developed."
msgstr ""
#: ../../extending/newtypes.rst:598
msgid "https://github.com/python/cpython"
msgstr "https://github.com/python/cpython"
#: ../../extending/newtypes.rst:56
msgid "object"
msgstr "objeto"
#: ../../extending/newtypes.rst:56
msgid "deallocation"
msgstr ""
#: ../../extending/newtypes.rst:56
msgid "deallocation, object"
msgstr ""
#: ../../extending/newtypes.rst:56
msgid "finalization"
msgstr ""
#: ../../extending/newtypes.rst:56
msgid "finalization, of objects"
msgstr ""
#: ../../extending/newtypes.rst:91
msgid "PyErr_Fetch (C function)"
msgstr ""
#: ../../extending/newtypes.rst:91
msgid "PyErr_Restore (C function)"
msgstr ""
#: ../../extending/newtypes.rst:150
msgid "string"
msgstr "string"
#: ../../extending/newtypes.rst:150
msgid "object representation"
msgstr ""
#: ../../extending/newtypes.rst:150
msgid "built-in function"
msgstr "função embutida"
#: ../../extending/newtypes.rst:150
msgid "repr"
msgstr "repr"