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 bethard
Recipients BreamoreBoy, bethard, draghuram, odd_bloke, r.david.murray
Date 2010-07-23.12:35:26
SpamBayes Score 0.00806487
Marked as misclassified No
Message-id <1279888528.76.0.541765923313.issue4297@psf.upfronthosting.co.za>
In-reply-to
Content
Not sure, but I think _print_message in argparse isn't exactly what the OP is looking for if they really only care about errors. If you want to override how errors are printed, then it's absolutely correct to override the error method (in argparse at least), and your overridden method should be given every message that is normally printed as an error.

If by errors, you mean "anything the parser might print out" (e.g. the output of "--help"), then you may indeed want _print_message to become public so you can override it. Let me know.
History
Date User Action Args
2010-07-23 12:35:28bethardsetrecipients: + bethard, draghuram, odd_bloke, r.david.murray, BreamoreBoy
2010-07-23 12:35:28bethardsetmessageid: <1279888528.76.0.541765923313.issue4297@psf.upfronthosting.co.za>
2010-07-23 12:35:27bethardlinkissue4297 messages
2010-07-23 12:35:26bethardcreate