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 pitrou
Recipients ezio.melotti, giampaolo.rodola, gvanrossum, michael.foord, pitrou
Date 2013-05-05.11:29:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> OTOH it's a useful option to have in case you're tracking down
> something that happens (or doesn't happen) when an object is collected

IMO this is a good reason to implement your specific tearDown method (or call addCleanup if you prefer), possibly in a shared base class.

I don't think this is a good candidate for a command-line option, it's too specialized and it's also not something which should be enabled blindly. In other words, each test case should know whether it needs a collection or not.
Date User Action Args
2013-05-05 11:29:55pitrousetrecipients: + pitrou, gvanrossum, giampaolo.rodola, ezio.melotti, michael.foord
2013-05-05 11:29:55pitrousetmessageid: <>
2013-05-05 11:29:55pitroulinkissue17908 messages
2013-05-05 11:29:55pitroucreate