[issue14449] argparse optional arguments should follow getopt_long(3)

Ernest N. Mamikonyan report at bugs.python.org
Sun Apr 1 15:18:23 CEST 2012


Ernest N. Mamikonyan <ernest.mamikonyan at gmail.com> added the comment:

Yes, it is incompatible. But that's because the current behavior is 
incompatible with standard (getopt_long(3)) practice. Or perhaps, you 
can add another option that implements the optional argument semantics 
of GNU's getopt_long(3).

In any case, I understand. If you figure out some other way, please let 
me know (or document it).

Thanks much,
Ernest Mamikonyan

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue14449>
_______________________________________


More information about the Python-bugs-list mailing list