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 serhiy.storchaka
Recipients axitkhurana, barry, dablanc, ezio.melotti, michael.foord, r.david.murray, rbcollins, serhiy.storchaka, vajrasky
Date 2018-09-27.08:01:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
There is a design issue with the order of cleaning up. tearDown() is purposed to release resources acquired in setUp(). Resources acquired in test methods will be released in doCleanup() if use addCleanup(), but since doCleanup() is called after tearDown(), resources will be released not in reversed order of the time of acquiring. This causes issues if resources acquired in a test method depends on the resource acquired in setUp().

Adding doClassCleanups() and doModuleCleanups() with the same semantic will introduce this problem at class and module level.
Date User Action Args
2018-09-27 08:01:07serhiy.storchakasetrecipients: + serhiy.storchaka, barry, rbcollins, ezio.melotti, r.david.murray, michael.foord, axitkhurana, vajrasky, dablanc
2018-09-27 08:01:06serhiy.storchakasetmessageid: <>
2018-09-27 08:01:06serhiy.storchakalinkissue24412 messages
2018-09-27 08:01:06serhiy.storchakacreate