Author kristjan.jonsson
Recipients Jim.Jewett, amaury.forgeotdarc, asvetlov, dstanek, isoschiz, kristjan.jonsson, loewis, pconnell, pitrou, rhettinger, serhiy.storchaka, stutzbach, tim.peters
Date 2018-06-04.10:11:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1528107106.02.0.592728768989.issue9141@psf.upfronthosting.co.za>
In-reply-to
Content
Hi there!  By the time pep 442 was introduced, I wasn't very active in python core stuff anymore, and still am not.

The intent of this patch, which is explained (IMHO) quite clearly in the first few comments was to

- Formalize a way for custom objects to tell GC "No, please don't delete my references _at this time_ because if you do, I will have to run non-trivial code that may wreak havoc".  This is different from just having a __del__ method.  Sometimes deleting is okay.  Sometimes not. 
- Make this way available to all objects, not just Generator objects.  We already identified a separate such instance in stackless python and it seemed prudent to "give back" the generalization that we made there for the benefit of python at large.
- Not introduce new slots for this purpose.

Now, with pep 442, I have no idea how Generators can postpone being garbage collection since I'm honestly not familiar with how things work now.

I have no particular skin in this game anymore, I'm no longer actively working on Stackless or Python integrations and I stopped trying to push stuff thought the bugtracker to preserve my sanity.

So, lets just close this until the day in the future when needs arise once more :)
History
Date User Action Args
2018-06-04 10:11:46kristjan.jonssonsetrecipients: + kristjan.jonsson, tim.peters, loewis, rhettinger, amaury.forgeotdarc, pitrou, dstanek, stutzbach, asvetlov, Jim.Jewett, serhiy.storchaka, pconnell, isoschiz
2018-06-04 10:11:46kristjan.jonssonsetmessageid: <1528107106.02.0.592728768989.issue9141@psf.upfronthosting.co.za>
2018-06-04 10:11:46kristjan.jonssonlinkissue9141 messages
2018-06-04 10:11:45kristjan.jonssoncreate