Changes by Antoine Pitrou pit...@free.fr:
--
resolution: wont fix - out of date
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12075
___
___
Antoine Pitrou added the comment:
Yes, __del__ will interfere with garbage collection before Python 3.4. This is
pretty much expected (and is fixed in Python 3.4, but won't be backported).
--
nosy: +pitrou
resolution: - wont fix
stage: - committed/rejected
status: open - closed
Changes by Terry J. Reedy tjre...@udel.edu:
--
versions: +Python 3.4 -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12075
___
___
Changes by Arfrever Frehtes Taifersar Arahesis arfrever@gmail.com:
--
nosy: +Arfrever
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12075
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12075
___
___
Terry J. Reedy tjre...@udel.edu added the comment:
my class also inherits from subprocess.Popen, which has a __del__ method,
which might interfere w/ collection
The doc says __del__ *will* prevent collection.
(although gc.garbage says otherwise ;).
Do you mean that gc.garbage is empty,
