[issue9044] [optparse] confusion over an option and its value without any space in between

Georg Brandl added the comment: Yes, this is common behavior and should not change. -- nosy: +georg.brandl resolution: -> works for me status: open -> closed ___ Python tracker

[issue9044] [optparse] confusion over an option and its value without any space in between

Brian Curtin added the comment: 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). -- nosy: +brian.curtin versions: +Python 3.2 -Python 2.6

[issue9044] [optparse] confusion over an option and its value without any space in between

New submission from Krzysztof Szawala : 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 . Based on the above syntax the following statement will be correct: -exclusiv