[Python-3000] Removing __del__

Nick Coghlan ncoghlan at gmail.com
Fri Sep 22 18:49:55 CEST 2006

Raymond Hettinger wrote:
> FWIW, don't despair on your original bold proposal.  While it's fun to
> free associate and generate ideas for new atrocities, I think most of
> your respondants are just kicking ideas around.

Who, us? ;)

> In the spirit of Py3k development, I recommend being quick to remove and
> slow to add.  Let 3.0 emerge without __del__ and if strong use cases
> emerge, there can be a 3.1 PEP for a new magic method.  I think Py3k
> should be as lean as possible and then build-up very slowly afterwards,
> emphasizing cruft-removal instead of cruft-substitution.

I'd be fine with this too (my suggestion for updated __del__ semantics was 
pure syntactic sugar for a weakref based solution), but I don't think I use 
__del__ enough for my vote on this particular topic to mean anything :)


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-3000 mailing list