[Python-Dev] PyObject_GC_UnTrack() no longer reliable in 2.7? (original) (raw)
Daniel Stutzbach daniel at stutzbachenterprises.com
Fri Sep 24 23:22:15 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 ]
On Fri, Sep 24, 2010 at 4:09 PM, "Martin v. Löwis" <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)
-- Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises, LLC <http://stutzbachenterprises.com/> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20100924/05ec2224/attachment.html>
- 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 ]