setUp being called twice is not an error
Bug #882884 reported by
Robert Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
testtools |
Fix Released
|
Wishlist
|
Robert Collins |
Bug Description
But like bug 508200 this indicates broken user code.
E.g.
>>> class T(testtools.
... def setUp(self):
... super(T, self).setUp()
... super(T, self).setUp()
... def test_foo(self):
... pass
...
>>> T('test_foo')()
<testtools.
>>>
Changed in testtools: | |
importance: | Medium → Wishlist |
Changed in testtools: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I hit this problem again today in a round-about-way; due to logging setup done in setUp() logger calls started to disappear only after the second call. This would have saved a fair bit of debugging