any optparse branches floating around

[Robert Collins]

On Thu, 2006-05-25 at 15:53 +1000, 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.
> 
> Before I do - does anyone have a patch/branch to use optparse instead of
> handcoded parsing?  There seemed to be a consensus this would be a good
> thing to do?

What do you want out of optparse specifically? I have some very neat
things I hacked up hanging around somewhere, - argument validation, and
handling for the things we do with diff (i.e. a grammar like
(branch branch) | (file ...) can be managed by my optparse branch, with
validation and more).


Rob


-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060525/174d464c/attachment.pgp