[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: I've just found issue #7936, which looks like the same problem. I'm going to close this issue as a duplicate of that one; further discussion should be moved there. -- resolution: -> duplicate status: open -> closed superseder: -> sys.argv contains

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: ftype Python.File Python.File="E:\Python31\python.exe" "%1" %* -- ___ Python tracker ___ ___ Python-bug

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: Okay, thanks. What does ftype Python.File give? -- ___ Python tracker ___ ___ Python-bugs-list ma

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: assoc .py .py=Python.File I tried this now with Ubuntu and Python 3.1.2 and all works fine. But under Windows XP it doesn't work. -- ___ Python tracker _

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: I'm failing to reproduce this on Windows 7, too. It sounds as though you're starting the python script without an explict 'python'. What are your filetype associations for python scripts? i.e., what's the result of typing 'assoc py' at a console prompt? And

[issue8984] Python 3 doesn't register script arguments

Changes by Antoine Pitrou : -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: I have already installed Python 3.1.2 a second time. I have selected during the installation that the files shall be compiled into bytecode. -- components: +Library (Lib) -Interpreter Core ___ Python tracker

[issue8984] Python 3 doesn't register script arguments

Éric Araujo added the comment: 3.0 should not be used and does not get fixes. Can you try downloading Python again and testing? P.S. please do not change the component; Lib means “Python files under Lib/ in the source checkout”, but sys is a module built by the interpreter core. -- c

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: I'm using Windows XP Professional SP3. I downloaded Python 3.1.2 from this site. Even Python 3.0.1 hasn't worked. -- components: +Library (Lib) -Interpreter Core ___ Python tracker _

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: Hmm. I don't see any difference between the two here (OS X 10.6). What platform are you on, and where did your copy of Python 3.1.2 come from? newton:~ dickinsm$ cat test.py import sys print(sys.argv[1]) newton:~ dickinsm$ python3.1 test.py 1234 1234 newton:

[issue8984] Python 3 doesn't register script arguments

Éric Araujo added the comment: Can’t reproduce here: $ python3.1 -c "import sys; print(sys.argv[1])" 1234 1234 $ python3.1 --version Python 3.1.2 -- components: +Interpreter Core -Library (Lib) nosy: +merwok ___ Python tracker

[issue8984] Python 3 doesn't register script arguments

Sworddragon added the comment: Examplescript test.py: import sys print(sys.argv[1]) Call this script now with an argument, for exmaple: test.py 1234 I expect to see the string 1234 in the console but Python 3 says "IndexError: list index out of range". With Python 2.6.5 I be able to see the

[issue8984] Python 3 doesn't register script arguments

Mark Dickinson added the comment: It's not entirely clear to me what issue you're reporting here: could you provide a short example script that exhibits the problem, and list the exact steps necessary to reproduce, along with actual and expected results? -- nosy: +mark.dickinson ___

[issue8984] Python 3 doesn't register script arguments

New submission from Sworddragon : Python 3.1.2 hasn't any arguments except the file name in sys.argv[0]. For example: build.py test sys.argv[1] will be empty. I tried even the first example from the documentation 15.4 (optparse) but the filename is None. In Python 2.6.5 all is working fine. -