➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Oren Milman, geeknik, lemburg, pitrou, serhiy.storchaka, tim.peters, twouters, vstinner
Date 2017-10-06.20:12:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507320768.39.0.213398074469.issue31165@psf.upfronthosting.co.za>
In-reply-to
Content 
"Maybe we should prevent collection of garbage with circular references (that has __del__() or weakref callbacks) from PyObject_GC_New()?"

That would be a major change in the garbage collector. I would prefer to not touch the GC, any change can introduce a complex regression.

Running the GC when an object is allocated makes sense to me. It's to reclaim memory, and prevent a MemoryError which would only be caused by "missed GC".
History
Date User Action Args
2017-10-06 20:12:48vstinnersetrecipients: + vstinner, lemburg, tim.peters, twouters, pitrou, serhiy.storchaka, Oren Milman, geeknik
2017-10-06 20:12:48vstinnersetmessageid: <1507320768.39.0.213398074469.issue31165@psf.upfronthosting.co.za>
2017-10-06 20:12:48vstinnerlinkissue31165 messages
2017-10-06 20:12:48vstinnercreate