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 kristjan.jonsson
Recipients Yury.Selivanov, asvetlov, ebfe, jimjjewett, kristjan.jonsson, lehmannro, pitrou, stutzbach
Date 2010-12-25.06:52:05
SpamBayes Score 0.0014377747
Marked as misclassified No
Message-id <1293259929.36.0.886396962828.issue10576@psf.upfronthosting.co.za>
In-reply-to
Content
Well, the idea is good and it did cross my mind.  Particularly it could be useful for performance sensitive applications.
However it complicates things.
1) If a GC is rejected, when do we make the next attempt?
2) If a callback cancels GC, then what about the other callbacks that have already been called?  They would need to get some "canceled" call.  But this is ok, I suppose.

Since we have already passed the beta 2, I'll see if I can come up with a simple change, particularly if we don't descend into some infinite loop wrt. 1) above.
History
Date User Action Args
2010-12-25 06:52:09kristjan.jonssonsetrecipients: + kristjan.jonsson, jimjjewett, pitrou, lehmannro, stutzbach, ebfe, asvetlov, Yury.Selivanov
2010-12-25 06:52:09kristjan.jonssonsetmessageid: <1293259929.36.0.886396962828.issue10576@psf.upfronthosting.co.za>
2010-12-25 06:52:05kristjan.jonssonlinkissue10576 messages
2010-12-25 06:52:05kristjan.jonssoncreate