Kumar McMillan added the comment:
I like this patch. However, a nice-to-have would be that _doCleanups()
prints a traceback from function(*args, **kwargs) (if there is one) the
same way that atexit does. That would aid in debugging mis-written
cleanup functions yet would not intrude on your
Changes by Kumar McMillan :
--
nosy: +kumar303
___
Python tracker
<http://bugs.python.org/issue5679>
___
___
Python-bugs-list mailing list
Unsubscribe:
Kumar McMillan added the comment:
For the record, I too have been plagued by failing setUp's :( and the
pattern you describe is not uncommon. I was just pointing out that
changing the semantics of tearDown() will affect a lot of existing code.
As with any backwards incompatible chang
Kumar McMillan added the comment:
fwiw, changing tearDown() so that it executes unconditionally will break
a countless number of test suites. No test suite since the dawn of
unittest has been designed to tearDown() what may not have been setUp()
correctly.
in other words, this is how [in my
Changes by Kumar McMillan <[EMAIL PROTECTED]>:
--
nosy: +kumar303
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue4554>
___
__
New submission from Kumar McMillan <[EMAIL PROTECTED]>:
Using Sphinx 0.4.1 I noticed a slight display bug in rendering
:show-inheritance: for a class with a PEP 8 / PEP 257 style docstring.
i.e. multi-line docstrings are recommended by the PEPs to look like:
class Foo(SomeFoo):
"
