Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #49369
| Date | 2013-06-28 05:57 -0500 |
|---|---|
| From | Andrew Berg <robotsondrugs@gmail.com> |
| Subject | Re: Why is the argparse module so inflexible? |
| References | <51CC897E.5000702@stoneleaf.us> <20130627230213.GA22992@cskk.homeip.net> <20130627192221.19949fa6@bigbox.christie.dr> <CAEk9e3rZwWCJbZaTfBnDpKyaD4o4UhMbGZCBm2hZgtmqLu7aDQ@mail.gmail.com> <51CD12DE.7030802@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.3955.1372417105.3114.python-list@python.org> (permalink) |
After getting over the hurdles I initially explained and moving forward, I've found that standard command-line parsing and its conventions are far too ingrained in the design of argparse to make it useful as a general command parser. I think I would end up overriding a substantial amount of the module to make it do what I want, and I would really rather not try to shoehorn one paradigm into another. Unfortunately, getopt provides none of the benefits I sought with argparse, and optparse is deprecated, so I will probably be rolling my own custom parser. -- CPython 3.3.2 | Windows NT 6.2.9200 / FreeBSD 9.1
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Why is the argparse module so inflexible? Andrew Berg <robotsondrugs@gmail.com> - 2013-06-28 05:57 -0500
csiph-web