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 gward
Recipients ajaksu2, akuchling, drtimcouper, gward
Date 2009-06-02.00:17:17
SpamBayes Score 1.831123e-06
Marked as misclassified No
Message-id <1243901840.51.0.0963345730661.issue1704474@psf.upfronthosting.co.za>
In-reply-to
Content
I just took a look at the original patch uploaded by drtimcouper.  IMHO
it would be cleaner and simpler to modify optparse.py so that it behaves
as consistently as possible under Jython and CPython.  For example,
optparse should catch the ValueError raised when a user supplies a bad
integer input and raise a new exception with a consistent error message.
 That sort of thing.

drtimcouper: if you're still out there and reading this, would you mind
submitting a new patch?
History
Date User Action Args
2009-06-02 00:17:21gwardsetrecipients: + gward, akuchling, ajaksu2, drtimcouper
2009-06-02 00:17:20gwardsetmessageid: <1243901840.51.0.0963345730661.issue1704474@psf.upfronthosting.co.za>
2009-06-02 00:17:18gwardlinkissue1704474 messages
2009-06-02 00:17:17gwardcreate