Antoine Pitrou added the comment:
The GC behaves gracefully in 3.4: the gc_bug script shows no uncollectable
object. I don't think this is worth fixing in 3.3.
--
nosy: +pitrou
resolution: - out of date
status: open - pending
versions: -Python 3.4
Christian Heimes added the comment:
I agree with not fixing 3.3.
--
status: pending - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1540
___
Changes by Antoine Pitrou pit...@free.fr:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1540
___
___
Python-bugs-list
Christian Heimes added the comment:
ping :)
--
versions: -Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1540
___
___
Python-bugs-list
Amaury Forgeot d'Arc added the comment:
Is the error still current? io.StringIO is now completely implemented in
_io/textio.c, and should not have any Python-level __del__.
--
___
Python tracker rep...@bugs.python.org
Christian Heimes added the comment:
I don't know ... Is somebody able to test it?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1540
___
___
Changes by Christian Heimes li...@cheimes.de:
--
stage: - patch review
type: - behavior
versions: +Python 3.2, Python 3.3, Python 3.4 -Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1540
Mark Lawrence breamore...@yahoo.co.uk added the comment:
Can we have an update on this please as it seems important.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1540
Jeremy Hylton jhyl...@gmail.com added the comment:
Amaury-- I think that will work. I put together a small patch that seems to
pass all the tests, but it too messy. We need some care to make sure we don't
spin forever if there's some degenerate case where we never escape GC.
--
Jeremy Hylton jhyl...@gmail.com added the comment:
I'm trying to figure out the attached script. If I run Python 3.0, the script
doesn't run because of the undefined gc.DEBUG_OBJECTS. If I just remove that,
the script runs without error. Does that mean the problem is fixed? Or is
running
Jeremy Hylton jhyl...@gmail.com added the comment:
I spent some time to understand the example script today. The specific issue
is that a set of objects get put into the list of unreachable objects with
finalizers (both Immutable and Finalizer instances). When Cycle's __dict__ is
cleared,
Jeremy Hylton jhyl...@gmail.com added the comment:
One last thought on this bug. The problem is that after we try to delete
garbage, we really can't know much about the state of the objects in the
finalizers list. If any of the objects that are cleared end up causing a
finalizer to run,
Guido van Rossum added the comment:
Hoping to draw Tim into this... He's the only one I know who truly
understands these issues...
--
assignee: - tim_one
nosy: +tim_one
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1540
New submission from Christian Heimes:
I've seen the problem on Windows only. test_doctest fails and the
problem also causes test_gc to fail when it is run after test_doctest.
W/o a prior run of test_doctest test_gc doesn't fail.
File c:\dev\python\py3k\lib\test\test_doctest.py, line 1570, in
14 matches
Mail list logo
