Roundup Robot devnull@devnull added the comment:
New changeset d6abdd78d2af by Michael Foord in branch '2.7':
Issue #10979. unittest stdout buffering now works for class and module fixtures.
http://hg.python.org/cpython/rev/d6abdd78d2af
--
nosy: +python-dev
Roundup Robot devnull@devnull added the comment:
New changeset 0f7036ea0930 by Michael Foord in branch '3.2':
Issue #10979. unittest stdout buffering now works with class and module setup
and teardown.
http://hg.python.org/cpython/rev/0f7036ea0930
--
Roundup Robot devnull@devnull added the comment:
New changeset 9c09ba72136e by Michael Foord in branch 'default':
Closes issue 10979. unittest buffering now works with class and module setup
and teardown
http://hg.python.org/cpython/rev/9c09ba72136e
--
resolution: - fixed
stage: -
Changes by Michael Foord mich...@voidspace.org.uk:
--
versions: +Python 3.2, Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10979
___
Michael Foord mich...@voidspace.org.uk added the comment:
Thanks for finding this Brandon. The same problem probably exists for
setupmodule and the teardown variants too.
The issue is that the sys.stdout manipulation is done by result.startTest but
setUpClass and setUpModule are executed by
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10979
___
___
Changes by Michael Foord mich...@voidspace.org.uk:
--
assignee: - michael.foord
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10979
___
___
New submission from Brandon Craig Rhodes bran...@rhodesmill.org:
Normally, unittest cleanly reports an exception in a setUpClass method. But if
I place the attached test in a directory by itself and then run python -m
unittest discover -b from inside of the same directory, then instead of
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +michael.foord
type: crash - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10979
___
