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, pitrou, rbcollins
Date 2009-04-04.21:56:49
SpamBayes Score 2.6218922e-08
Marked as misclassified No
Message-id <1238882210.77.0.991586339971.issue5679@psf.upfronthosting.co.za>
In-reply-to
Content
Actually let me phrase that differently.
standard practice for setUp is
super.setUp()
my_setup_code()

and tearDown is
my_teardown_code()
super.tearDown()

because of the LIFO need.

If you imagine that clean ups are being done in the base class teardown,
at the end of that method, then it becomes a lot more obvious why it
should run after tearDown - because thats the right place, and because
many users may be failing to call the base class tearDown which has
historically done nothing.
History
Date User Action Args
2009-04-04 21:56:50rbcollinssetrecipients: + rbcollins, gregory.p.smith, pitrou, michael.foord
2009-04-04 21:56:50rbcollinssetmessageid: <1238882210.77.0.991586339971.issue5679@psf.upfronthosting.co.za>
2009-04-04 21:56:49rbcollinslinkissue5679 messages
2009-04-04 21:56:49rbcollinscreate