Comment 2 for bug 1456353

I would like to comment that this sounds like a great idea. We've stumbled upon this issue here: [1], and specifically the discussion about this is here: [2].

I do think that this is quite an API change - developers might not except this change to happen (for example, a cleanUp code that was registered assumes that a setUp has been successful and won't check for it, causing the cleanUp to fail). I wonder if there's a non-invasive way to fix this gradually (maybe add a flag to useFixture that would, over time, become the default?)
This might be off base though, so I'd like to hear thoughts about this from others as well.

[1]: https://review.openstack.org/#/c/181991/
[2]: https://review.openstack.org/#/c/181991/1..4/neutron/tests/fullstack/fullstack_fixtures.py