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 j1m
Recipients j1m
Date 2010-09-01.19:01:12
SpamBayes Score 1.1466883e-11
Marked as misclassified No
Message-id <1283367674.32.0.228375766546.issue9736@psf.upfronthosting.co.za>
In-reply-to
Content
We often run test suites repeatedly using a debug build of python
to look for memory leaks.

We also got in the bad habit of using a fork of doctest. Recently, we've switched away from our fork and have noticed a problem with the standard doctest's handling of test globs (globals).

DocTestSuite gets an initial set of globals from the module the doctest's came from.  After running the tests, it seems to clear these, leading to errors if the tests are run again.

I've attached a script that illustrates the problem.  The script runs a simple test twice and gets a spurious failure the second time.
History
Date User Action Args
2010-09-01 19:01:14j1msetrecipients: + j1m
2010-09-01 19:01:14j1msetmessageid: <1283367674.32.0.228375766546.issue9736@psf.upfronthosting.co.za>
2010-09-01 19:01:13j1mlinkissue9736 messages
2010-09-01 19:01:12j1mcreate