[issue2821] unittest.py sys.exit error

Mark Fitzgerald added the comment: Agreed that this is clearly not a bug. One way to get the desired behavior from IDLE is to move up to Python 2.7a0+ or Python 3.1.1+, where the 'exit' parameter of unittest.main(), which when set to False, disables the sys.exit() call. Alternatively, in 2.5,

[issue2821] unittest.py sys.exit error

Michael Foord added the comment: IDLE catches the SystemExit function raised by TestProgram().runTests() and prints the traceback. Not a bug in unittest. -- nosy: +michael.foord resolution: -> works for me status: open -> closed ___ Python tracker

[issue2821] unittest.py sys.exit error

J. Pablo Fernández <[EMAIL PROTECTED]> added the comment: Shouldn't this be closed now? or is there anything pending to be solved? -- nosy: +pupeno ___ Python tracker <[EMAIL PROTECTED]> _

[issue2821] unittest.py sys.exit error

ndl [mailto:[EMAIL PROTECTED] > Sent: Monday, May 12, 2008 9:22 AM > To: Getchell, Adam > Subject: [issue2821] unittest.py sys.exit error > > > Georg Brandl <[EMAIL PROTECTED]> added the comment: > > This is an IDLE problem then. > > -- > assignee

[issue2821] unittest.py sys.exit error

Georg Brandl <[EMAIL PROTECTED]> added the comment: This is an IDLE problem then. -- assignee: -> kbk components: +IDLE -Library (Lib) nosy: +kbk __ Tracker <[EMAIL PROTECTED]> __ ___

[issue2821] unittest.py sys.exit error

Georg Brandl <[EMAIL PROTECTED]> added the comment: Can you elaborate how you get the printed exception? When running your code as a script under 2.5 or trunk, I don't get such a message. -- nosy: +georg.brandl __ Tracker <[EMAIL PROTECTED]>

[issue2821] unittest.py sys.exit error

New submission from Adam Getchell <[EMAIL PROTECTED]>: Picking the canonical example of unit test: import random import unittest class TestSequenceFunctions(unittest.TestCase): def setUp(self): self.seq = range(10) def testshuffle(self): # make sure the shuffled se