[issue10979] setUpClass exception causes explosion with "-b"

2011-03-17 Thread Roundup Robot 

Roundup Robot  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:  -> committed/rejected
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10979] setUpClass exception causes explosion with "-b"

2011-03-17 Thread Roundup Robot 

Roundup Robot  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

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10979] setUpClass exception causes explosion with "-b"

2011-03-17 Thread Roundup Robot 

Roundup Robot  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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10979] setUpClass exception causes explosion with "-b"

2011-03-16 Thread Michael Foord 

Michael Foord  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 the suite outside the normal 
startTest / stopTest cycle. 

I think the answer is to have the stdout manipulation done in separate result 
methods (called by stopTest / startTest) that can also be called by the suite 
around the setup / teardown of class and module.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10979] setUpClass exception causes explosion with "-b"

2011-03-16 Thread Michael Foord 

Changes by Michael Foord :


--
versions: +Python 3.2, Python 3.3

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10979] setUpClass exception causes explosion with "-b"

2011-02-02 Thread Ezio Melotti 

Changes by Ezio Melotti :


--
nosy: +ezio.melotti

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10979] setUpClass exception causes explosion with "-b"

2011-01-23 Thread Michael Foord 

Changes by Michael Foord :


--
assignee:  -> michael.foord

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10979] setUpClass exception causes explosion with "-b"

2011-01-21 Thread R. David Murray 

Changes by R. David Murray :


--
nosy: +michael.foord
type: crash -> behavior

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue10979] setUpClass exception causes explosion with "-b"

2011-01-21 Thread Brandon Craig Rhodes 

New submission from Brandon Craig Rhodes :

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 being 
shown the setUpClass exception I am instead shown a long traceback because 
unittest seems to think that it has put a stringIO in place of sys.stdout but a 
file is there instead.

--
components: Library (Lib)
files: test_example.py
messages: 126816
nosy: brandon-rhodes
priority: normal
severity: normal
status: open
title: setUpClass exception causes explosion with "-b"
type: crash
versions: Python 2.7
Added file: http://bugs.python.org/file20484/test_example.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com