This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients ethan.furman, ncoghlan
Date 2012-02-28.11:30:20
SpamBayes Score 1.5926744e-07
Marked as misclassified No
Message-id <1330428621.93.0.707130481762.issue14136@psf.upfronthosting.co.za>
In-reply-to
Content
test_cmd_line and test_cmd_line_script are both about testing the behaviour of the interpreter when run from the command line. Since this test *is* a behavioural test for the interpreter when invoked as an application, it should be in one of them.

The former is for testing the behaviour that doesn't involve invoking a script that does something, whereas the latter is for testing the way the interpreter handles various methods of script invocation, *including* what it prints to stderr and stdout in various scenarios.

Therefore, test_cmd_line_script *is* the right place for it. The fact that it happens to be testing the way an exception is displayed doesn't change the fact that it's a test of the way the interpreter handles a particular situation that may arise when running a script.
History
Date User Action Args
2012-02-28 11:30:21ncoghlansetrecipients: + ncoghlan, ethan.furman
2012-02-28 11:30:21ncoghlansetmessageid: <1330428621.93.0.707130481762.issue14136@psf.upfronthosting.co.za>
2012-02-28 11:30:21ncoghlanlinkissue14136 messages
2012-02-28 11:30:20ncoghlancreate