[issue29130] Exit code 120 returned from Python unit test testing SystemExit

2017-01-03 Thread R. David Murray
Changes by R. David Murray : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

2017-01-03 Thread John Hagen
John Hagen added the comment: I'm completely fine with closing this issue. Thanks for the help everyone. If someone else doesn't close it in a couple days, I'll do it. -- ___ Python tracker

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

2017-01-03 Thread STINNER Victor
STINNER Victor added the comment: This issue is not a bug in Python, but a bug in the author's code. I suggest to close the issue, since enough clues have been provided to fix the author's issue. -- nosy: +haypo ___ Python tracker

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

2017-01-02 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: > Having said all that, perhaps it would be reasonable to tolerate a missing > flush() method, and not treat this as an error. In all cases the flush() method is called unconditionally. I think it can be considered as mandatory part of the writer protocol.

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

2017-01-02 Thread Martin Panter
Martin Panter added the comment: David is right. The 120 code was added in Issue 5319, as a way of indicating a problem in the final stages of the interpreter exiting. The two conditions that trigger this are calling the flush() method on sys.stdout and sys.stderr. If you add a dummy flush()

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

2017-01-02 Thread Xiang Zhang
Xiang Zhang added the comment: Behaviour changed in #5319. Add author Martin. -- nosy: +martin.panter, xiang.zhang ___ Python tracker ___

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

2017-01-01 Thread R. David Murray
R. David Murray added the comment: My guess would be that the problem that your NullWriter doesn't have a flush method. But I'm not familiar with this change, so I'm just guessing. -- nosy: +r.david.murray ___ Python tracker

[issue29130] Exit code 120 returned from Python unit test testing SystemExit

2017-01-01 Thread John Hagen
New submission from John Hagen: I recently tried to port one of my packages to Python 3.6 and unit tests that worked in Python 2.7, 3.3-3.5 began failing in 3.6. I originally thought it was a problem with coverage, but it turns out it was not. The full thread is: