[issue1540] Refleak tests: test_doctest and test_gc are failing

2013-10-23 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue1540] Refleak tests: test_doctest and test_gc are failing

2013-10-23 Thread Christian Heimes
Christian Heimes added the comment: I agree with not fixing 3.3. -- status: pending -> open ___ Python tracker ___ ___ Python-bugs-list

[issue1540] Refleak tests: test_doctest and test_gc are failing

2013-10-23 Thread Antoine Pitrou
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 __

[issue1540] Refleak tests: test_doctest and test_gc are failing

2013-10-21 Thread Christian Heimes
Christian Heimes added the comment: I don't know ... Is somebody able to test it? -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue1540] Refleak tests: test_doctest and test_gc are failing

2013-10-21 Thread Amaury Forgeot d'Arc
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 ___

[issue1540] Refleak tests: test_doctest and test_gc are failing

2013-10-21 Thread Christian Heimes
Christian Heimes added the comment: ping :) -- versions: -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue1540] Refleak tests: test_doctest and test_gc are failing

2012-11-26 Thread Christian Heimes
Changes by Christian Heimes : -- stage: -> patch review type: -> behavior versions: +Python 3.2, Python 3.3, Python 3.4 -Python 3.0 ___ Python tracker ___ __

[issue1540] Refleak tests: test_doctest and test_gc are failing

2010-09-18 Thread Mark Lawrence
Mark Lawrence added the comment: Can we have an update on this please as it seems important. -- nosy: +BreamoreBoy ___ Python tracker ___

[issue1540] Refleak tests: test_doctest and test_gc are failing

2010-02-19 Thread Jeremy Hylton
Jeremy Hylton 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. -- _

[issue1540] Refleak tests: test_doctest and test_gc are failing

2010-02-18 Thread Jeremy Hylton
Jeremy Hylton 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, then any of the objec

[issue1540] Refleak tests: test_doctest and test_gc are failing

2010-02-18 Thread Jeremy Hylton
Jeremy Hylton 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, it also decrefs Imm

[issue1540] Refleak tests: test_doctest and test_gc are failing

2010-02-18 Thread Jeremy Hylton
Jeremy Hylton 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 without an error a

[issue1540] Refleak tests: test_doctest and test_gc are failing

2007-12-05 Thread Guido van Rossum
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]> __

[issue1540] Refleak tests: test_doctest and test_gc are failing

2007-12-05 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: Finally I found a potential problem with the garbage collector in a specific case: - Some object C participates in a reference cycle, and contains a reference to another object X. - X.__del__ 'resurrect' the object, by saving its 'self' somewhere else. - X

[issue1540] Refleak tests: test_doctest and test_gc are failing

2007-12-04 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: After some hard debugging: - doctest.debug_src() is unlucky enough to trigger a garbage collection just when compiling the given code. - gc collects unreachable objects, among them is an instance of the class doctest._SpoofOut, which derives from io.StringI

[issue1540] Refleak tests: test_doctest and test_gc are failing

2007-12-02 Thread Christian Heimes
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 t