Repository navigation
Expand file tree
/
Copy pathgcsupport.po
More file actions
645 lines (542 loc) · 20.1 KB
/
Copy pathgcsupport.po
File metadata and controls
645 lines (542 loc) · 20.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
# Copyright (C) 2001-2018, Python Software Foundation
# For licence information, see README file.
#
msgid ""
msgstr ""
"Project-Id-Version: Python 3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-10-17 14:27+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: c-api/gcsupport.rst:6
msgid "Supporting Cyclic Garbage Collection"
msgstr ""
#: c-api/gcsupport.rst:8
msgid ""
"Python's support for detecting and collecting garbage which involves "
"circular references requires support from object types which are "
"\"containers\" for other objects which may also be containers. Types which "
"do not store references to other objects, or which only store references to "
"atomic types (such as numbers or strings), do not need to provide any "
"explicit support for garbage collection."
msgstr ""
#: c-api/gcsupport.rst:15
msgid ""
"To create a container type, the :c:member:`~PyTypeObject.tp_flags` field of "
"the type object must include the :c:macro:`Py_TPFLAGS_HAVE_GC` and provide "
"an implementation of the :c:member:`~PyTypeObject.tp_traverse` handler. If "
"instances of the type are mutable, a :c:member:`~PyTypeObject.tp_clear` "
"implementation must also be provided."
msgstr ""
#: c-api/gcsupport.rst:21
msgid ":c:macro:`Py_TPFLAGS_HAVE_GC`"
msgstr ""
#: c-api/gcsupport.rst:22
msgid ""
"Objects with a type with this flag set must conform with the rules "
"documented here. For convenience these objects will be referred to as "
"container objects."
msgstr ""
#: c-api/gcsupport.rst:26
msgid "Constructors for container types must conform to two rules:"
msgstr ""
#: c-api/gcsupport.rst:28
msgid ""
"The memory for the object must be allocated using :c:macro:`PyObject_GC_New` "
"or :c:macro:`PyObject_GC_NewVar`."
msgstr ""
#: c-api/gcsupport.rst:31
msgid ""
"Once all the fields which may contain references to other containers are "
"initialized, it must call :c:func:`PyObject_GC_Track`."
msgstr ""
#: c-api/gcsupport.rst:34
msgid ""
"Similarly, the deallocator for the object must conform to a similar pair of "
"rules:"
msgstr ""
#: c-api/gcsupport.rst:37
msgid ""
"Before fields which refer to other containers are "
"invalidated, :c:func:`PyObject_GC_UnTrack` must be called."
msgstr ""
#: c-api/gcsupport.rst:40
msgid ""
"The object's memory must be deallocated using :c:func:`PyObject_GC_Del`."
msgstr ""
#: c-api/gcsupport.rst:43
msgid ""
"If a type adds the Py_TPFLAGS_HAVE_GC, then it *must* implement at least "
"a :c:member:`~PyTypeObject.tp_traverse` handler or explicitly use one from "
"its subclass or subclasses."
msgstr ""
#: c-api/gcsupport.rst:47
msgid ""
"When calling :c:func:`PyType_Ready` or some of the APIs that indirectly call "
"it like :c:func:`PyType_FromSpecWithBases` or :c:func:`PyType_FromSpec` the "
"interpreter will automatically populate "
"the :c:member:`~PyTypeObject.tp_flags`, :c:member:`~PyTypeObject.tp_traverse` "
"and :c:member:`~PyTypeObject.tp_clear` fields if the type inherits from a "
"class that implements the garbage collector protocol and the child class "
"does *not* include the :c:macro:`Py_TPFLAGS_HAVE_GC` flag."
msgstr ""
#: c-api/gcsupport.rst:57
msgid ""
"Analogous to :c:macro:`PyObject_New` but for container objects with "
"the :c:macro:`Py_TPFLAGS_HAVE_GC` flag set."
msgstr ""
#: c-api/gcsupport.rst:84
msgid ""
"Do not call this directly to allocate memory for an object; call the "
"type's :c:member:`~PyTypeObject.tp_alloc` slot instead."
msgstr ""
#: c-api/gcsupport.rst:87
msgid ""
"When populating a type's :c:member:`~PyTypeObject.tp_alloc` "
"slot, :c:func:`PyType_GenericAlloc` is preferred over a custom function that "
"simply calls this macro."
msgstr ""
#: c-api/gcsupport.rst:91
msgid ""
"Memory allocated by this macro must be freed with :c:func:`PyObject_GC_Del` "
"(usually called via the object's :c:member:`~PyTypeObject.tp_free` slot)."
msgstr ""
#: c-api/gcsupport.rst:97
msgid ":c:func:`PyObject_GC_Del`"
msgstr ""
#: c-api/gcsupport.rst:74
msgid ":c:macro:`PyObject_New`"
msgstr ""
#: c-api/gcsupport.rst:99 c-api/gcsupport.rst:193
msgid ":c:func:`PyType_GenericAlloc`"
msgstr ""
#: c-api/gcsupport.rst:100
msgid ":c:member:`~PyTypeObject.tp_alloc`"
msgstr ""
#: c-api/gcsupport.rst:81
msgid ""
"Analogous to :c:macro:`PyObject_NewVar` but for container objects with "
"the :c:macro:`Py_TPFLAGS_HAVE_GC` flag set."
msgstr ""
#: c-api/gcsupport.rst:98
msgid ":c:macro:`PyObject_NewVar`"
msgstr ""
#: c-api/gcsupport.rst:105
msgid ""
"Analogous to :c:macro:`PyObject_GC_New` but allocates *extra_size* bytes at "
"the end of the object (at offset :c:member:`~PyTypeObject.tp_basicsize`). "
"The allocated memory is initialized to zeros, except for the :c:type:`Python "
"object header <PyObject>`."
msgstr ""
#: c-api/gcsupport.rst:111
msgid ""
"The extra data will be deallocated with the object, but otherwise it is not "
"managed by Python."
msgstr ""
#: c-api/gcsupport.rst:114
msgid ""
"Memory allocated by this function must be freed "
"with :c:func:`PyObject_GC_Del` (usually called via the "
"object's :c:member:`~PyTypeObject.tp_free` slot)."
msgstr ""
#: c-api/gcsupport.rst:119
msgid ""
"The function is marked as unstable because the final mechanism for reserving "
"extra data after an instance is not yet decided. For allocating a variable "
"number of fields, prefer using :c:type:`PyVarObject` "
"and :c:member:`~PyTypeObject.tp_itemsize` instead."
msgstr ""
#: c-api/gcsupport.rst:130
msgid ""
"Resize an object allocated by :c:macro:`PyObject_NewVar`. Returns the "
"resized object of type ``TYPE*`` (refers to any C type) or ``NULL`` on "
"failure."
msgstr ""
#: c-api/gcsupport.rst:134
msgid ""
"*op* must be of type :c:expr:`PyVarObject *` and must not be tracked by the "
"collector yet. *newsize* must be of type :c:type:`Py_ssize_t`."
msgstr ""
#: c-api/gcsupport.rst:141
msgid ""
"Adds the object *op* to the set of container objects tracked by the "
"collector. The collector can run at unexpected times so objects must be "
"valid while being tracked. This should be called once all the fields "
"followed by the :c:member:`~PyTypeObject.tp_traverse` handler become valid, "
"usually near the end of the constructor."
msgstr ""
#: c-api/gcsupport.rst:150
msgid ""
"Returns non-zero if the object implements the garbage collector protocol, "
"otherwise returns 0."
msgstr ""
#: c-api/gcsupport.rst:153
msgid ""
"The object cannot be tracked by the garbage collector if this function "
"returns 0."
msgstr ""
#: c-api/gcsupport.rst:158
msgid ""
"Returns 1 if the object type of *op* implements the GC protocol and *op* is "
"being currently tracked by the garbage collector and 0 otherwise."
msgstr ""
#: c-api/gcsupport.rst:161
msgid "This is analogous to the Python function :func:`gc.is_tracked`."
msgstr ""
#: c-api/gcsupport.rst:168
msgid ""
"Returns 1 if the object type of *op* implements the GC protocol and *op* has "
"been already finalized by the garbage collector and 0 otherwise."
msgstr ""
#: c-api/gcsupport.rst:171
msgid "This is analogous to the Python function :func:`gc.is_finalized`."
msgstr ""
#: c-api/gcsupport.rst:178
msgid ""
"Releases memory allocated to an object using :c:macro:`PyObject_GC_New` "
"or :c:macro:`PyObject_GC_NewVar`."
msgstr ""
#: c-api/gcsupport.rst:181
msgid ""
"Do not call this directly to free an object's memory; call the "
"type's :c:member:`~PyTypeObject.tp_free` slot instead."
msgstr ""
#: c-api/gcsupport.rst:184
msgid ""
"Do not use this for memory allocated "
"by :c:macro:`PyObject_New`, :c:macro:`PyObject_NewVar`, or related "
"allocation functions; use :c:func:`PyObject_Free` instead."
msgstr ""
#: c-api/gcsupport.rst:190
msgid ":c:func:`PyObject_Free` is the non-GC equivalent of this function."
msgstr ""
#: c-api/gcsupport.rst:191
msgid ":c:macro:`PyObject_GC_New`"
msgstr ""
#: c-api/gcsupport.rst:192
msgid ":c:macro:`PyObject_GC_NewVar`"
msgstr ""
#: c-api/gcsupport.rst:194
msgid ":c:member:`~PyTypeObject.tp_free`"
msgstr ""
#: c-api/gcsupport.rst:199
msgid ""
"Remove the object *op* from the set of container objects tracked by the "
"collector. Note that :c:func:`PyObject_GC_Track` can be called again on "
"this object to add it back to the set of tracked objects. The deallocator "
"(:c:member:`~PyTypeObject.tp_dealloc` handler) should call this for the "
"object before any of the fields used by "
"the :c:member:`~PyTypeObject.tp_traverse` handler become invalid."
msgstr ""
#: c-api/gcsupport.rst:208
msgid ""
"The :c:func:`!_PyObject_GC_TRACK` and :c:func:`!_PyObject_GC_UNTRACK` macros "
"have been removed from the public C API."
msgstr ""
#: c-api/gcsupport.rst:211
msgid ""
"The :c:member:`~PyTypeObject.tp_traverse` handler accepts a function "
"parameter of this type:"
msgstr ""
#: c-api/gcsupport.rst:216
msgid ""
"Type of the visitor function passed to "
"the :c:member:`~PyTypeObject.tp_traverse` handler. The function should be "
"called with an object to traverse as *object* and the third parameter to "
"the :c:member:`~PyTypeObject.tp_traverse` handler as *arg*. The Python core "
"uses several visitor functions to implement cyclic garbage detection; it's "
"not expected that users will need to write their own visitor functions."
msgstr ""
#: c-api/gcsupport.rst:223
msgid ""
"The :c:member:`~PyTypeObject.tp_clear` handler must be of "
"the :c:type:`inquiry` type, or ``NULL`` if the object is immutable."
msgstr ""
#: c-api/gcsupport.rst:229
msgid ""
"Drop references that may have created reference cycles. Immutable objects "
"do not have to define this method since they can never directly create "
"reference cycles. Note that the object must still be valid after calling "
"this method (don't just call :c:func:`Py_DECREF` on a reference). The "
"collector will call this method if it detects that this object is involved "
"in a reference cycle."
msgstr ""
#: c-api/gcsupport.rst:240
msgid "Traversal"
msgstr ""
#: c-api/gcsupport.rst:242
msgid ""
"The :c:member:`~PyTypeObject.tp_traverse` handler must have the following "
"type:"
msgstr ""
#: c-api/gcsupport.rst:246
msgid ""
"Traversal function for a garbage-collected object, used by the garbage "
"collector to detect reference cycles. Implementations must call the *visit* "
"function for each object directly contained by *self*, with the parameters "
"to *visit* being the contained object and the *arg* value passed to the "
"handler. The *visit* function must not be called with a ``NULL`` object "
"argument. If *visit* returns a non-zero value, that value should be "
"returned immediately."
msgstr ""
#: c-api/gcsupport.rst:255
msgid ""
"A typical :c:member:`!tp_traverse` function calls the :c:func:`Py_VISIT` "
"convenience macro on each of the instance's members that are Python objects "
"that the instance owns. For example, this is a (slightly outdated) traversal "
"function for the :py:class:`threading.local` class::"
msgstr ""
#: c-api/gcsupport.rst:273
msgid ""
":c:func:`Py_VISIT` requires the *visit* and *arg* parameters to :c:func:`!"
"local_traverse` to have these specific names; don't name them just anything."
msgstr ""
#: c-api/gcsupport.rst:277
msgid ""
"Instances of :ref:`heap-allocated types <heap-types>` hold a reference to "
"their type. Their traversal function must therefore visit the type::"
msgstr ""
#: c-api/gcsupport.rst:282
msgid ""
"Alternately, the type may delegate this responsibility by calling "
"``tp_traverse`` of a heap-allocated superclass (or another heap-allocated "
"type, if applicable). If they do not, the type object may not be garbage-"
"collected."
msgstr ""
#: c-api/gcsupport.rst:287
msgid ""
"If the :c:macro:`Py_TPFLAGS_MANAGED_DICT` bit is set in "
"the :c:member:`~PyTypeObject.tp_flags` field, the traverse function must "
"call :c:func:`PyObject_VisitManagedDict` like this::"
msgstr ""
#: c-api/gcsupport.rst:296
msgid ""
"Only the members that the instance *owns* (by having :term:`strong "
"references <strong reference>` to them) must be visited. For instance, if an "
"object supports weak references via "
"the :c:member:`~PyTypeObject.tp_weaklist` slot, the pointer supporting the "
"linked list (what *tp_weaklist* points to) must **not** be visited as the "
"instance does not directly own the weak references to itself."
msgstr ""
#: c-api/gcsupport.rst:303
msgid "The traversal function has a limitation:"
msgstr ""
#: c-api/gcsupport.rst:307
msgid ""
"The traversal function must not have any side effects. Implementations may "
"not modify the reference counts of any Python objects nor create or destroy "
"any Python objects, directly or indirectly."
msgstr ""
#: c-api/gcsupport.rst:311
msgid ""
"This means that *most* Python C API functions may not be used, since they "
"can raise a new exception, return a new reference to a result object, have "
"internal logic that uses side effects. Also, unless documented otherwise, "
"functions that happen to not have side effects may start having them in "
"future versions, without warning."
msgstr ""
#: c-api/gcsupport.rst:317
msgid ""
"For a list of safe functions, see a :ref:`separate section <duringgc-"
"functions>` below."
msgstr ""
#: c-api/gcsupport.rst:322
msgid ""
"The :c:func:`Py_VISIT` call may be skipped for those members that provably "
"cannot participate in reference cycles. In the ``local_traverse`` example "
"above, there is also a ``self->key`` member, but it can only be ``NULL`` or "
"a Python string and therefore cannot be part of a reference cycle."
msgstr ""
#: c-api/gcsupport.rst:328
msgid ""
"On the other hand, even if you know a member can never be part of a cycle, "
"as a debugging aid you may want to visit it anyway just so the :mod:`gc` "
"module's :func:`~gc.get_referents` function will include it."
msgstr ""
#: c-api/gcsupport.rst:334
msgid ""
"The :c:member:`~PyTypeObject.tp_traverse` function can be called from any "
"thread."
msgstr ""
#: c-api/gcsupport.rst:339
msgid ""
"Garbage collection is a \"stop-the-world\" operation: even in :term:`free "
"threading` builds, only one thread state is :term:`attached <attached thread "
"state>` when :c:member:`!tp_traverse` handlers run."
msgstr ""
#: c-api/gcsupport.rst:346
msgid ""
"Heap-allocated types are expected to visit ``Py_TYPE(self)`` in "
"``tp_traverse``. In earlier versions of Python, due to `bug 40217 <https://"
"bugs.python.org/issue40217>`_, doing this may lead to crashes in subclasses."
msgstr ""
#: c-api/gcsupport.rst:351
msgid ""
"To simplify writing :c:member:`~PyTypeObject.tp_traverse` handlers, "
"a :c:func:`Py_VISIT` macro is provided. In order to use this macro, "
"the :c:member:`~PyTypeObject.tp_traverse` implementation must name its "
"arguments exactly *visit* and *arg*:"
msgstr ""
#: c-api/gcsupport.rst:358
msgid ""
"If the :c:expr:`PyObject *` *o* is not ``NULL``, call the *visit* callback, "
"with arguments *o* and *arg*. If *visit* returns a non-zero value, then "
"return it."
msgstr ""
#: c-api/gcsupport.rst:362
msgid "This corresponds roughly to::"
msgstr ""
#: c-api/gcsupport.rst:374
msgid "Traversal-safe functions"
msgstr ""
#: c-api/gcsupport.rst:376
msgid ""
"The following functions and macros are safe to use in "
"a :c:member:`~PyTypeObject.tp_traverse` handler:"
msgstr ""
#: c-api/gcsupport.rst:379
msgid "the *visit* function passed to ``tp_traverse``"
msgstr ""
#: c-api/gcsupport.rst:380
msgid ":c:func:`Py_VISIT`"
msgstr ""
#: c-api/gcsupport.rst:381
msgid ":c:func:`Py_SIZE`"
msgstr ""
#: c-api/gcsupport.rst:382
msgid ""
":c:func:`Py_TYPE`: if called from a :c:member:`!tp_traverse` "
"handler, :c:func:`!Py_TYPE`'s result will be valid for the duration of the "
"handler call"
msgstr ""
#: c-api/gcsupport.rst:384
msgid ":c:func:`PyObject_VisitManagedDict`"
msgstr ""
#: c-api/gcsupport.rst:385
msgid ":c:func:`PyObject_TypeCheck`, :c:func:`PyType_IsSubtype`, :c:func:`PyType_HasFeature`"
msgstr ""
#: c-api/gcsupport.rst:387
msgid ""
":samp:`Py{<type>}_Check` and :samp:`Py{<type>}_CheckExact` -- for "
"example, :c:func:`PyTuple_Check`"
msgstr ""
#: c-api/gcsupport.rst:389
msgid ":ref:`duringgc-functions`"
msgstr ""
#: c-api/gcsupport.rst:394
msgid "\"DuringGC\" functions"
msgstr ""
#: c-api/gcsupport.rst:396
msgid ""
"The following functions should *only* be used in "
"a :c:member:`~PyTypeObject.tp_traverse` handler; calling them in other "
"contexts may have unintended consequences."
msgstr ""
#: c-api/gcsupport.rst:400
msgid ""
"These functions act like their counterparts without the ``_DuringGC`` "
"suffix, but they are guaranteed to not have side effects, they do not set an "
"exception on failure, and they return/set :term:`borrowed references "
"<borrowed reference>` as detailed in the individual documentation."
msgstr ""
#: c-api/gcsupport.rst:405
msgid ""
"Note that these functions may fail (return ``NULL`` or ``-1``), but as they "
"do not set an exception, no error information is available. In some cases, "
"failure is not distinguishable from a successful ``NULL`` result."
msgstr ""
#: c-api/gcsupport.rst:430 c-api/gcsupport.rst:443
msgid "See :ref:`duringgc-functions` for common information."
msgstr ""
#: c-api/gcsupport.rst:421
msgid ":c:func:`PyObject_GetTypeData`, :c:func:`PyObject_GetItemData`, :c:func:`PyType_GetModuleState`, :c:func:`PyModule_GetState`, :c:func:`PyModule_GetToken`, :c:func:`PyType_GetBaseByToken`"
msgstr ""
#: c-api/gcsupport.rst:432
msgid ""
"Sets *\\*result* to a :term:`borrowed reference` rather than a strong one. "
"The reference is valid for the duration of the :c:member:`!tp_traverse` "
"handler call."
msgstr ""
#: c-api/gcsupport.rst:438
msgid ":c:func:`PyType_GetBaseByToken`"
msgstr ""
#: c-api/gcsupport.rst:445
msgid ""
"These functions return a :term:`borrowed reference`, which is valid for the "
"duration of the :c:member:`!tp_traverse` handler call."
msgstr ""
#: c-api/gcsupport.rst:452
msgid ":c:func:`PyType_GetModule`, :c:func:`PyType_GetModuleByToken`"
msgstr ""
#: c-api/gcsupport.rst:457
msgid "Controlling the Garbage Collector State"
msgstr ""
#: c-api/gcsupport.rst:459
msgid ""
"The C-API provides the following functions for controlling garbage "
"collection runs."
msgstr ""
#: c-api/gcsupport.rst:464
msgid ""
"Perform a full garbage collection, if the garbage collector is enabled. "
"(Note that :func:`gc.collect` runs it unconditionally.)"
msgstr ""
#: c-api/gcsupport.rst:467
msgid ""
"Returns the number of collected + unreachable objects which cannot be "
"collected. If the garbage collector is disabled or already collecting, "
"returns ``0`` immediately. Errors during garbage collection are passed "
"to :data:`sys.unraisablehook`. This function does not raise exceptions."
msgstr ""
#: c-api/gcsupport.rst:477
msgid ""
"Enable the garbage collector: similar to :func:`gc.enable`. Returns the "
"previous state, 0 for disabled and 1 for enabled."
msgstr ""
#: c-api/gcsupport.rst:485
msgid ""
"Disable the garbage collector: similar to :func:`gc.disable`. Returns the "
"previous state, 0 for disabled and 1 for enabled."
msgstr ""
#: c-api/gcsupport.rst:493
msgid ""
"Query the state of the garbage collector: similar to :func:`gc.isenabled`. "
"Returns the current state, 0 for disabled and 1 for enabled."
msgstr ""
#: c-api/gcsupport.rst:500
msgid "Querying Garbage Collector State"
msgstr ""
#: c-api/gcsupport.rst:502
msgid ""
"The C-API provides the following interface for querying information about "
"the garbage collector."
msgstr ""
#: c-api/gcsupport.rst:507
msgid ""
"Run supplied *callback* on all live GC-capable objects. *arg* is passed "
"through to all invocations of *callback*."
msgstr ""
#: c-api/gcsupport.rst:511
msgid ""
"If new objects are (de)allocated by the callback it is undefined if they "
"will be visited."
msgstr ""
#: c-api/gcsupport.rst:514
msgid ""
"Garbage collection is disabled during operation. Explicitly running a "
"collection in the callback may lead to undefined behaviour e.g. visiting the "
"same objects multiple times or not at all."
msgstr ""
#: c-api/gcsupport.rst:522
msgid ""
"Type of the visitor function to be passed "
"to :c:func:`PyUnstable_GC_VisitObjects`. *arg* is the same as the *arg* "
"passed to ``PyUnstable_GC_VisitObjects``. Return ``1`` to continue "
"iteration, return ``0`` to stop iteration. Other return values are reserved "
"for now so behavior on returning anything else is undefined."
msgstr ""