Interleaved commands and options with optparse?

[David Goodger]

Magnus Lie Hetland wrote:
> In article <slrnb2upbe.d9h.mlh at furu.idi.ntnu.no>, Magnus Lie Hetland wrote:
> [snip]
>> Indeed. Quite useful. This really ought to be in the docs.

Doc patches would be welcome I'm sure (see below).

> And while I'm at it -- it ought to be an argument to the constructor,
> just like, for example, parser.usage (and most of the other
> attributes, it seems).
> 
> Anyone think that submitting a patch for this would be a bad idea?

Not at all -- potentially quite a good idea.  Best to discuss it on the
optik-users at lists.sf.net list, and patches to the http://optik.sf.net
project.  The Python stdlib "optparse" module is directly and automatically
derived from the Optik code.

-- 
David Goodger    http://starship.python.net/~goodger    Projects:
  * Python Docutils: http://docutils.sourceforge.net/
    (includes reStructuredText: http://docutils.sf.net/rst.html)
  * The Go Tools Project: http://gotools.sourceforge.net/