Created on 2010-06-21 16:05 by kszawala, last changed 2010-06-27 10:40 by georg.brandl. This issue is now closed.
| Messages (3) | |||
|---|---|---|---|
| msg108280 - (view) | Author: Krzysztof Szawala (kszawala) | Date: 2010-06-21 16:05 | |
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 |
|||
| msg108286 - (view) | Author: Brian Curtin (brian.curtin) *  |
Date: 2010-06-21 16:41 | |
I wouldn't say that is confusing -- it is a common usage to have an option immediately followed by it's value (see gcc output after running make, -Wall, etc). |
|||
| msg108780 - (view) | Author: Georg Brandl (georg.brandl) * |
Date: 2010-06-27 10:40 | |
Yes, this is common behavior and should not change. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-06-27 10:40:57 | georg.brandl | set | status: open -> closed nosy: + georg.brandl messages: + msg108780 resolution: works for me |
| 2010-06-21 16:41:44 | brian.curtin | set | nosy:
+ brian.curtin messages: + msg108286 versions: + Python 3.2, - Python 2.6 |
| 2010-06-21 16:05:30 | kszawala | create | |