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 ebfe
Recipients Yury.Selivanov, asvetlov, ebfe, jimjjewett, kristjan.jonsson, lehmannro, pitrou, stutzbach
Date 2010-12-26.17:05:06
SpamBayes Score 0.00014072335
Marked as misclassified No
Message-id <1293383109.83.0.0134973931287.issue10576@psf.upfronthosting.co.za>
In-reply-to
Content
Collection may re-occur at any time, there is no promise to the callback code. However, the callback can disable the gc, preventing further collection.

I don't think we need the other callbacks to be informed. As the callbacks are worked down in the order they registered, whoever comes first is served first. Returning True from the callback is mereley a "I dont mind if gc happens now..."
History
Date User Action Args
2010-12-26 17:05:10ebfesetrecipients: + ebfe, jimjjewett, pitrou, kristjan.jonsson, lehmannro, stutzbach, asvetlov, Yury.Selivanov
2010-12-26 17:05:09ebfesetmessageid: <1293383109.83.0.0134973931287.issue10576@psf.upfronthosting.co.za>
2010-12-26 17:05:06ebfelinkissue10576 messages
2010-12-26 17:05:06ebfecreate