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 michael.foord
Recipients benjamin.peterson, exarkun, fabioz, michael.foord
Date 2011-04-07.16:50:50
SpamBayes Score 0.00019695798
Marked as misclassified No
Message-id <1302195051.17.0.814087508081.issue11798@psf.upfronthosting.co.za>
In-reply-to
Content
A TestSuite (which is how tests are collected to run) holds all the tests and therefore keeps them all alive for the duration of the test run. (I presume this is the issue anyway.)

How would you solve this - by having calling a TestSuite (which is how a test run is executed) remove members from themselves after each test execution? (Any failure tracebacks etc stored by the TestResult would also have to not keep the test alive.)

My only concern would be backwards compatibility due to the change in behaviour.
History
Date User Action Args
2011-04-07 16:50:51michael.foordsetrecipients: + michael.foord, exarkun, fabioz, benjamin.peterson
2011-04-07 16:50:51michael.foordsetmessageid: <1302195051.17.0.814087508081.issue11798@psf.upfronthosting.co.za>
2011-04-07 16:50:50michael.foordlinkissue11798 messages
2011-04-07 16:50:50michael.foordcreate