Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #49369 > unrolled thread

Re: Why is the argparse module so inflexible?

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Why is the argparse module so inflexible? Andrew Berg <robotsondrugs@gmail.com> - 2013-06-28 05:57 -0500

#49369 — Re: Why is the argparse module so inflexible?

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

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web