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 andybuckley, bethard, eric.araujo, gruszczy, marcs, ndim, r.david.murray, wplappert, zbysz
Date 2012-02-24.09:59:38
SpamBayes Score 8.65769e-06
Marked as misclassified No
Message-id <1330077579.76.0.924851942829.issue4256@psf.upfronthosting.co.za>
In-reply-to
Content
So it seems like what bash needs and what zsh needs are pretty different. My feeling so far is that if there isn't "one true format" that argparse can produce and be useful to a wide variety of shells, then it's probably not functionality that belongs in Python core, and instead belongs on PyPI.

So I guess my recommended next step would be to have someone offer help to the maintainer of http://pypi.python.org/pypi/optcomplete to update it to support argparse as well. If and when optcomplete supports argparse, bash, zsh and whatever other common shells people are using, and when optcomplete has significant usage in the field, then we can consider integrating it into the Python stdlib.
History
Date User Action Args
2012-02-24 09:59:39bethardsetrecipients: + bethard, ndim, eric.araujo, wplappert, andybuckley, r.david.murray, zbysz, gruszczy, marcs
2012-02-24 09:59:39bethardsetmessageid: <1330077579.76.0.924851942829.issue4256@psf.upfronthosting.co.za>
2012-02-24 09:59:39bethardlinkissue4256 messages
2012-02-24 09:59:38bethardcreate