[issue4640] optparse - dosn't distinguish between '--option' and '-option'
New submission from Krzysztof Szawala : I am using optparse for command-line parameters parsing. To follow common naming convention I defined -d (minus followed by a single character option) and --debug (double minus followed by a word). It looks like optparse doesn't complain when -debug (single minus) is specified and morover it doesn't recognize it as --debug. I am using Python 2.5.2. Problem was observed on Linux but also occurs on Windows. -- components: Extension Modules messages: 77668 nosy: kszawala severity: normal status: open title: optparse - dosn't distinguish between '--option' and '-option' type: behavior versions: Python 2.5 ___ Python tracker <http://bugs.python.org/issue4640> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4641] optparse - dosn't distinguish between '--option' and '-option'
New submission from Krzysztof Szawala : I am using optparse for command-line parameters parsing. To follow common naming convention I defined -d (minus followed by a single character option) and --debug (double minus followed by a word). It looks like optparse doesn't complain when -debug (single minus) is specified and morover it doesn't recognize it as --debug. I am using Python 2.5.2. Problem was observed on Linux but also occurs on Windows. -- components: Extension Modules messages: 77669 nosy: kszawala severity: normal status: open title: optparse - dosn't distinguish between '--option' and '-option' type: behavior versions: Python 2.5 ___ Python tracker <http://bugs.python.org/issue4641> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4642] optparse - dosn't distinguish between '--option' and '-option'
New submission from Krzysztof Szawala : I am using optparse for command-line parameters parsing. To follow common naming convention I defined -d (minus followed by a single character option) and --debug (double minus followed by a word). It looks like optparse doesn't complain when -debug (single minus) is specified and morover it doesn't recognize it as --debug. I am using Python 2.5.2. Problem was observed on Linux but also occurs on Windows. -- components: Extension Modules messages: 77670 nosy: kszawala severity: normal status: open title: optparse - dosn't distinguish between '--option' and '-option' type: behavior versions: Python 2.5 ___ Python tracker <http://bugs.python.org/issue4642> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4640] optparse - dosn't distinguish between '--option' and '-option'
Krzysztof Szawala added the comment: As I mentionetd, the problem occurs with Python 2.5 (I won't be switching to Python 3). The only perspective for me to upgrade is Python 2.6, but as I can see the problem applies to 2.6 as well. ___ Python tracker <http://bugs.python.org/issue4640> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6985] range() fails with long integers
New submission from Krzysztof Szawala : range() method fails with the following error message: " Traceback (most recent call last): File "", line 1, in OverflowError: range() result has too many items " when passing a valid integer value of 99. This value is obtained from OptParse command-line option as a valid ingeter. Applies to both Windows and Linux (32 and 64-bit). -- components: Interpreter Core messages: 93063 nosy: kszawala severity: normal status: open title: range() fails with long integers type: crash versions: Python 2.6 ___ Python tracker <http://bugs.python.org/issue6985> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[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: -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 -- components: Library (Lib) messages: 108280 nosy: kszawala priority: normal severity: normal status: open title: [optparse] confusion over an option and its value without any space in between type: feature request versions: Python 2.6 ___ Python tracker <http://bugs.python.org/issue9044> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
