Message108280
| Author |
kszawala |
| Recipients |
kszawala |
| Date |
2010年06月21日.16:05:29 |
| SpamBayes Score |
0.036910336 |
| Marked as misclassified |
No |
| Message-id |
<1277136331.24.0.0452022727538.issue9044@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Currently optparse library supports the following option definitions:
-e value,
-e=value,
-e:value,
-evalue.
Having said that let's consider the following option definition:
-e <string_value>.
Based on the above syntax the following statement will be correct:
-exclusive
and will be parsed into -e xclusive.
The fact that no caracter is required in between the option itself and its value leads to confusion.
My suggestion is to restrict the syntax to the following:
-e value,
-e=value,
-e:value.
Thanks,
Krzysztof |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年06月21日 16:05:31 | kszawala | set | recipients:
+ kszawala |
| 2010年06月21日 16:05:31 | kszawala | set | messageid: <1277136331.24.0.0452022727538.issue9044@psf.upfronthosting.co.za> |
| 2010年06月21日 16:05:29 | kszawala | link | issue9044 messages |
| 2010年06月21日 16:05:29 | kszawala | create |
|