[issue9444] argparse does not honor prefix_chars when adding default options

2010-08-01 Thread Theodore Turocy
Theodore Turocy added the comment: I'm uploading a new version of my patch which includes a proposed clarification to the documentation about the behavior in this case. Doug, does this make the documentation clearer to you? It is now explicit about the behavior for formulating the

[issue9444] argparse does not honor prefix_chars when adding default options

2010-08-01 Thread Theodore Turocy
Theodore Turocy added the comment: I was less than clear in what I wrote last night, Doug. What I mean is that the idiom "::foo" for a long argument, instead of the more standard-looking "--foo", appears in the test suite. This suggests to me that the intended behavior

[issue9444] argparse does not honor prefix_chars when adding default options

2010-07-31 Thread Theodore Turocy
Theodore Turocy added the comment: Looking at the test fixtures that exercise argparse, it appears that the intended behavior when '-' is not a prefix_char is to accept a doubling of any of the prefix_chars for long arguments. That is, if '-' is not present in prefix_ch

[issue9444] argparse does not honor prefix_chars when adding default options

2010-07-31 Thread Theodore Turocy
Theodore Turocy added the comment: What is the appropriate behavior for long options when '-' is not one of the accepted prefix_chars? All of '-h', '--help', '-v', and '--version' are hardcoded in the ctor. If, for instance, prefix_chars=&#

[issue2244] urllib and urllib2 decode userinfo multiple times

2010-07-31 Thread Theodore Turocy
Theodore Turocy added the comment: I am attaching a patch against py3k which adds some tests to demonstrate the original bug when issuing a Request() to a ftp:// URL. To do this, the tests add checks for user and passwd. The previous version of checks asserted that the .user and .passwd of