[Python-Dev] PyObject_GC_UnTrack() no longer reliable in 2.7?

"Martin v. Löwis" martin at v.loewis.de
Sat Sep 25 00:10:39 CEST 2010

Am 24.09.2010 23:22, schrieb Daniel Stutzbach:
> On Fri, Sep 24, 2010 at 4:09 PM, "Martin v. Löwis" <martin at v.loewis.de
> <mailto:martin at v.loewis.de>> wrote:
>     I think it would be possible to have two versions of
>     _PyGC_REFS_UNTRACKED, one being, say, -5.
>     _PyGC_REFS_UNTRACKED_AND_KEEP_IT_THAT_WAY would be what you get
>     when you call PyObject_GC_UnTrack; the code to do automatic
>     tracking/untracking based on contents would use some other
>     new API (which would be non-public in 2.7.x).
> Where would the extra state information be stored? (to distinguish
> untracked and untracked-and-keep-it-that-way)

As everything else: in gc_refs.


More information about the Python-Dev mailing list