This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, christian.heimes
Date 2007-12-05.00:34:03
SpamBayes Score 0.043445118
Marked as misclassified No
Message-id <1196814844.22.0.13619065808.issue1540@psf.upfronthosting.co.za>
In-reply-to
Content
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.StringIO.
- The debugger steps into io.IOBase.__del__

Some possible directions:
- Change the gc thresholds. A very temporary workaround to make the test
pass.
- Find the cycle involving the SpoofOut object, and try to break it in
doctest.py.
- Find a way to disable pdb tracing when the gc is running finalizers.
(this is what happens in 2.5: pdb does not step into a C function)
- Forget everything, and wait for the io.py object to be rewritten in C.
History
Date User Action Args
2007-12-05 00:34:04amaury.forgeotdarcsetspambayes_score: 0.0434451 -> 0.043445118
recipients: + amaury.forgeotdarc, christian.heimes
2007-12-05 00:34:04amaury.forgeotdarcsetspambayes_score: 0.0434451 -> 0.0434451
messageid: <1196814844.22.0.13619065808.issue1540@psf.upfronthosting.co.za>
2007-12-05 00:34:04amaury.forgeotdarclinkissue1540 messages
2007-12-05 00:34:03amaury.forgeotdarccreate