Only point I'd add is that this makes the `setUp` behaviour of fixtures
different from the `setUp` of `TestCase`. If `TestCase.setUp` raises an
error, `TestCase.tearDown` is not run. This difference will probably
confuse people.
On Mon, 22 Jun 2015 at 03:20 Robert Collins <email address hidden>
wrote:
Good analysis.
Only point I'd add is that this makes the `setUp` behaviour of fixtures
different from the `setUp` of `TestCase`. If `TestCase.setUp` raises an
error, `TestCase.tearDown` is not run. This difference will probably
confuse people.
On Mon, 22 Jun 2015 at 03:20 Robert Collins <email address hidden>
wrote:
> I'm going to propose that we attach details to an exception and raise /rbtcollins. wordpress. com/2015/ 06/22/revisitin g-the-fixture- api- leaky-resources / /rbtcollins. wordpress. com/2015/ 06/22/revisitin g-the-fixture- api-handling- leaky-resources /> /bugs.launchpad .net/bugs/ 897190 /bugs.launchpad .net/python- fixtures/ +bug/897190/ +subscriptions
> that when setUp fails.
>
> https:/
> handling-
> <https:/
> is my analysis of why.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Details added in fixture cleanup are not gathered
>
> To manage notifications about this bug go to:
> https:/
>