This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author bethard
Recipients bethard, georg.brandl, travistouchdown
Date 2010-07-30.06:54:03
SpamBayes Score 0.0073290234
Marked as misclassified No
Message-id <1280472844.99.0.841079198435.issue9399@psf.upfronthosting.co.za>
In-reply-to
Content
The equivalent to optparse callback is basically to define __call__ in a subclass of Action. Pretty much the same amount of work because they both have complicated parameters.

The "callable" I (not fully confidently) proposed would just be a shorthand for defining __call__ in a subclass of Action when you don't care about any of the other command line info.

I guess, without further use cases for "callable" and given that you can subclass Action for other use cases, let's just do the action='write' version. Feel free to supply a patch, or I will when I get some time for argparse again.
History
Date User Action Args
2010-07-30 06:54:05bethardsetrecipients: + bethard, georg.brandl, travistouchdown
2010-07-30 06:54:04bethardsetmessageid: <1280472844.99.0.841079198435.issue9399@psf.upfronthosting.co.za>
2010-07-30 06:54:03bethardlinkissue9399 messages
2010-07-30 06:54:03bethardcreate