[issue16142] ArgumentParser inconsistent with parse_known_args

2013-02-02 Thread Radu Ciorba

Radu Ciorba added the comment:

"- if the unknown option is given first then both options are treated as 
unknown and returned in the list of remaining arguments."
I don't think this case is correct behaviour. There is no way to determine if u 
accepts arguments or not. If nargs for -u is "?" or more, the current behavior 
is correct since everything after -u would be an argument for this option.

--
nosy: +Radu.Ciorba

___
Python tracker 
<http://bugs.python.org/issue16142>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue16468] argparse only supports iterable choices

2013-02-02 Thread Radu Ciorba

Changes by Radu Ciorba :


--
nosy: +Radu.Ciorba

___
Python tracker 
<http://bugs.python.org/issue16468>
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com