[issue5538] tearDown in unittest should be executed regardless of result in setUp

[Garrett Cooper]

Garrett Cooper <yanegomi at gmail.com> added the comment:

And maybe the addCleanup components could be a stack of callable objects?

This would make life easier for folks like me and would make the overall
flow much cleaner / clearer as it would allow us to break things down
into atomic steps which could be reverted in a LIFO order.

Steve / Raymond: Do you guys like Jean-Paul's proposal? If so, I'll
write up a patch sometime this coming weekend to implement that
functionality.

For now I'll just call tearDown blindly on Exceptions *shivers*.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5538>
_______________________________________