Re: patch for whitespace in help output
Greg Ward <[email protected]> Sun, 7 Sep 2003 10:56:02 -0400
| Newsgroups | gmane.comp.python.optik.user |
|---|---|
| Message-ID | <[email protected]> |
On 26 August 2003, David Goodger said:
> Checked in for optik, but I'm having trouble reconciling with
> Python's CVS. Optik's option_parser.py is quite different from
> the corresponding portion of Python's optparse.py. Which is
> authoritative?
For the record, Optik's CVS is authoritative. Python's optparse.py is
derived from Optik using the 'merge' script at the top of the Optik CVS
tree.
> The change is at revision 1.55 (optik's CVS).
> The change that was made was much more than the checkin message
> indicated (deleted STD_HELP_OPTION, STD_VERSION_OPTION; added
> _add_version_option, _add_help_option methods).
Oh bugger; I did indeed screwup the checkin. That really should have
been two distinct checkins, but it's too late now. At least CVS lets me
change the checkin message, which is now:
revision 1.55
date: 2003/06/22 20:04:50; author: gward; state: Exp; lines: +16 -15
Revert part of the last checkin: error() should use print_usage() to
print the usage message; no need to duplicate the logic in
print_usage().
Remove STD_HELP_OPTION and STD_VERSION_OPTION, and replace them with
_add_version_option() and _add_help_option() -- anyone who wants to
override the standard help/version options can just subclass OptionParser
and override these methods.
Now, for my next trick, I'm going to modify Optik's 'merge' script so it
puts the revision numbers for the Optik source files into Python's
optparse.py...
Greg
--
Greg Ward <[email protected]> http://www.gerg.ca/
Never underestimate the power of human stupidity.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf