[issue2674] unittest.TestProgram uses sys.exit()

Daniel Diniz added the comment: Closing as issue 3379 has more discussion and patch. -- nosy: +ajaksu2 priority: -> normal resolution: -> duplicate status: open -> closed superseder: -> Option to not-exit on test ___ Python tracker

[issue2674] unittest.TestProgram uses sys.exit()

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: I was bothered by this 'bug' ages ago, and I was work-arounding it. So now I've spent some time in 'fixing' it with the patches on issue #3379. -- nosy: +pupeno ___ Python tracker <[EMAIL PROTE

[issue2674] unittest.TestProgram uses sys.exit()

Facundo Batista <[EMAIL PROTECTED]> added the comment: That class is normally used at the end of the testing suite, as is recommended in the documentation. In any case, I don't see that like a bug, so we shouldn't be changing that behaviour, because of compatibility. What do you think? Maybe th

[issue2674] unittest.TestProgram uses sys.exit()

New submission from Johan Tufvesson <[EMAIL PROTECTED]>: The class TestProgram (and its synonym "main") in module unittest is (probably) meant to be an easy way to use the functionality of the module unittest. It is very surprising (and error-prone) that it uses sys.exit() with a status code inst