[issue3379] Option to not-exit on test

Michael Foord added the comment: No, make that revision 72191. :-) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue3379] Option to not-exit on test

Michael Foord added the comment: Committed in revision 71291. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list ma

[issue3379] Option to not-exit on test

Michael Foord added the comment: Correct patch this time. If there are no objections I'll apply this in a couple of days. -- Added file: http://bugs.python.org/file13790/unittest-no-exit.patch ___ Python tracker _

[issue3379] Option to not-exit on test

Michael Foord added the comment: Damn somehow managed to upload the patch to the wrong issue twice in a row. Must have been late at night. -- ___ Python tracker ___ _

[issue3379] Option to not-exit on test

Changes by Michael Foord : Removed file: http://bugs.python.org/file13784/unittest-no-exit.patch ___ Python tracker ___ ___ Python-bugs-list ma

[issue3379] Option to not-exit on test

Benjamin Peterson added the comment: Michael, this patch seems to include extra addCleanup() stuff. -- ___ Python tracker ___ ___ Pyth

[issue3379] Option to not-exit on test

Michael Foord added the comment: Patch that adds the same exit functionality, but also stores the result as an instance attribute on the return TestProgram instance. As this functionality has been requested several times my intention is to apply this patch. -- Added file: http://bugs.p

[issue3379] Option to not-exit on test

Michael Foord added the comment: Not returning the results is not a problem - if you needed access to the results you would hardly be using this API in the first place. The obvious use case if for running tests from an interactive environment where you are using the visual output on stdout. If

[issue3379] Option to not-exit on test

Changes by Daniel Diniz : -- components: +Tests priority: -> normal stage: -> patch review versions: +Python 2.7, Python 3.1 -Python 3.0 ___ Python tracker ___ _

[issue3379] Option to not-exit on test

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: What about always returning the results. Granted, when sys.exit is run there will be no results returned, but then nothing to get the results. If we divided in two functions, would one be unittest.main and the other unittest.nonExitingMain

[issue3379] Option to not-exit on test

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I still think a different method would be better for the no-exit functionality. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3379] Option to not-exit on test

Georg Brandl <[EMAIL PROTECTED]> added the comment: Well, the results are displayed on stdout like they are if sys.exit is used. As the first post explains, the use-case is running the tests from an interactive interpreter. ___ Python tracker <[EMAIL PROTECTED

[issue3379] Option to not-exit on test

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: I'm not sure it's a good idea. When exit=False, don't you lose the results? It would be better to return the results, but then that makes for an ugly API (changing the return value based on an argument is a general no-no in Python). It wou

[issue3379] Option to not-exit on test

Georg Brandl <[EMAIL PROTECTED]> added the comment: Barry, this looks useful and shouldn't be at all disruptive even after beta2. May I check it in? -- assignee: -> barry nosy: +barry, georg.brandl ___ Python tracker <[EMAIL PROTECTED]>

[issue3379] Option to not-exit on test

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Added tests. Added file: http://bugs.python.org/file10929/add_avoid_exit_option.diff ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3379] Option to not-exit on test

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Added some documentation. Added file: http://bugs.python.org/file10909/add_avoid_exit_option.diff ___ Python tracker <[EMAIL PROTECTED]> _

[issue3379] Option to not-exit on test

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Indeed this patch can be considered a fix for #2674, but, it should be documented appropriately. Should that be in http://docs.python.org/dev/3.0/library/unittest.html ? ___ Python tracker <[EMAIL PROTE

[issue3379] Option to not-exit on test

Changes by J. Pablo Fernández <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10906/add_avoid_exit_option.diff ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3379] Option to not-exit on test

Changes by J. Pablo Fernández <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file10908/add_avoid_exit_option.diff ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3379] Option to not-exit on test

Benjamin Peterson <[EMAIL PROTECTED]> added the comment: This is related to (maybe a duplicate of) #2674. -- nosy: +benjamin.peterson ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3379] Option to not-exit on test

New submission from J. Pablo Fernández <[EMAIL PROTECTED]>: Added an option, called exit, that when set to false, will make the tests not exit at the end. This is useful when you are doing Lisp-like development having a REPL (interpreter/prompt) opened in Emacs and running the tests over and over