any optparse branches floating around

[Martin Pool]

On 25 May 2006, John Arbash Meinel <john at arbash-meinel.com> wrote:
> Aaron Bentley wrote:
> > Martin Pool wrote:
> > | We just had #46432, where bzrtools accidentally overrides the
> > | description of another command's option.  I would like sometime to clean
> > | up the option code to make it less dependent on global definitions, e.g.
> > | in defining short names.
> > 
> > I don't think we'll see much more of that-- that part of bzrtools was
> > written when adding to OPTIONS was the only way to define new options.
> 
> Well, it was also for stuff like allowing '--long, --short, --line' to
> all set the same variable, rather than setting separate variables.
> And also to allow '-r 10 -r 20'.
> 
> We've pretty much kept the 'consistency' rule that short options always
> expand to the same long option. Which is very nice from a consistency
> standpoint, but does mean that there are places where we might like to
> have a short option, but can't.

I think consistency is good, but we can keep that other than by keeping
all the definitions in one place.  Perhaps just considering this when
assigning them is enough.

-- 
Martin