[Python-Dev] PyObject_GC_UnTrack() no longer reliable in 2.7? (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Sat Sep 25 00:10:39 CEST 2010
- Previous message: [Python-Dev] PyObject_GC_UnTrack() no longer reliable in 2.7?
- Next message: [Python-Dev] PyObject_GC_UnTrack() no longer reliable in 2.7?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 PyGCREFSUNTRACKED, one being, say, -5. PyGCREFSUNTRACKEDANDKEEPITTHATWAY would be what you get when you call PyObjectGCUnTrack; 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.
Regards, Martin
- Previous message: [Python-Dev] PyObject_GC_UnTrack() no longer reliable in 2.7?
- Next message: [Python-Dev] PyObject_GC_UnTrack() no longer reliable in 2.7?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]