[Python-3000] Removing __del__
krstic at solarsail.hcs.harvard.edu
Fri Sep 22 18:29:58 CEST 2006
Raymond Hettinger wrote:
> I'm on-board for just ripping out __del__. [...]
> 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.
+1, on all counts.
Ivan Krstić <krstic at solarsail.hcs.harvard.edu> | GPG: 0x147C722D
More information about the Python-3000