[issue5995] unittest command line behaviour

2009-05-12 Thread Michael Foord
Michael Foord added the comment: This commit caused a regression in command line behavior of modules using unittest.main(). Fixed in revision 72583. -- ___ Python tracker ___ ___

[issue5995] unittest command line behaviour

2009-05-11 Thread Michael Foord
Michael Foord added the comment: Committed in revision 72570. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list ma

[issue5995] unittest command line behaviour

2009-05-11 Thread Michael Foord
Michael Foord added the comment: I didn't add the issue number because I created the patch prior to creating the issue. Will add when I commit. Would like permission to commit this from an interested core developer. -- ___ Python tracker

[issue5995] unittest command line behaviour

2009-05-11 Thread Antoine Pitrou
Antoine Pitrou added the comment: It would be nice to have a test for the command line functionality but I'm not sure it's easy. In Misc/NEWS, please add the issue number as in other entries. Other than that, looks fine. -- keywords: -needs review nosy: +pitrou priority: -> normal res

[issue5995] unittest command line behaviour

2009-05-11 Thread Michael Foord
New submission from Michael Foord : This patch adds a verbosity keyword argument to unittest.main - so you can do: if __name__ == '__main__': unittest.main(verbosity=2) It also has a minor fix allowing you to specify test modules / classes from the command line. This enables unittest