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 paul.j3
Recipients A. Skrobov, docs@python, paul.j3, r.david.murray
Date 2015-10-03.21:13:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443906797.23.0.140315886069.issue25299@psf.upfronthosting.co.za>
In-reply-to
Content
The unittest file test_argparse.py tests add_argument parameters in 

    class TestInvalidArgumentConstructors(TestCase)

It looks at a dozen different categories of errors, mostly checking that they return the correct TypeError or ValueError.  It does not check the content of error messages.  

If I change the code I described yesterday to return a TypeError again (but with an enhanced message), it passes this unittest.

Most of the test_argparse.py tests just check for error type.  There just a couple of late additions that check error message content:

    TestMessageContentError
    TestAddArgumentMetavar
History
Date User Action Args
2015-10-03 21:13:17paul.j3setrecipients: + paul.j3, r.david.murray, docs@python, A. Skrobov
2015-10-03 21:13:17paul.j3setmessageid: <1443906797.23.0.140315886069.issue25299@psf.upfronthosting.co.za>
2015-10-03 21:13:17paul.j3linkissue25299 messages
2015-10-03 21:13:17paul.j3create