Optional Arguments on Tasks

[Christopher Hunter]

Forgive me if I've missed something, but I don't think I have.

Is there a way to create cmdopts that are optional? I guess I was hoping paver had a similar interface for this as say argparse. It would almost make more sense if they were by default optional and you specified a cmd option to be required.

Something like this would be usable:

@task

@cmdopts([

    ('port=', 'p', 'port', 'optional')

])

def start(options):

    """Start task for a MISL server process"""

    launch_app(options.port)

Chris

[Almad]

Hi,

Paver's @cmdopts is basically a wrapper around optparse. Thus, options
are all optional by default and there is no way to mark some as
required.

I'd say internals should be changed to be argparse-based and to extend
the @cmdopts tuples to have more options, argparse-style.

Patches welcome ;)

Lukas

2014/1/12 Christopher Hunter <hunter.ch...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups
> "paver" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to paver+un...@googlegroups.com.
> To post to this group, send email to pa...@googlegroups.com.
> Visit this group at http://groups.google.com/group/paver.
> For more options, visit https://groups.google.com/groups/opt_out.

[Christopher Hunter]

Ok, does it support the default flag from optparse?  Curious if there is any docs as to how that maps to the tuple.  

Chris