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 rbcollins
Recipients gregory.p.smith, michael.foord, ngie, pitrou, rbcollins, vdupras
Date 2009-04-05.23:54:58
SpamBayes Score 2.734979e-12
Marked as misclassified No
Message-id <1238975691.28697.39.camel@lifeless-64>
In-reply-to <>
On Sun, 2009-04-05 at 23:49 +0000, Michael Foord wrote:
> As an interesting data point, the Bzr code does clean ups *before*
> tearDown.

No it doesn't:

We subclass unittest.TestCase. We also override run() to make tearDown
run always.

Our base test case class has it's tearDown:

    def tearDown(self):
        self._bzr_test_tearDown_run = True
        self._log_contents = ''

(which is to say, _runCleanups runs after any child classes tearDown,
even though we implement it by calling it from our base-most tearDown).

Date User Action Args
2009-04-05 23:55:00rbcollinssetrecipients: + rbcollins, gregory.p.smith, pitrou, vdupras, ngie, michael.foord
2009-04-05 23:54:59rbcollinslinkissue5679 messages
2009-04-05 23:54:58rbcollinscreate