[issue7936] sys.argv contains only scriptname

Terry J. Reedy added the comment: I am closing this because there is no identifiable issue with the current installers. Initial issues were reported fixed. The most recent issue reported by Alecz was that installing 2.7 after 3.4 caused python files to be opened by 2.7. This is what shoul

[issue7936] sys.argv contains only scriptname

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue7936] sys.argv contains only scriptname

Mark Lawrence added the comment: @Alecz are you aware of the Python launcher, see https://www.python.org/dev/peps/pep-0397/ and https://docs.python.org/3/using/windows.html#python-launcher-for-windows ? The easiest way to sort out 3.4 would have been to download the msi file and use the repa

[issue7936] sys.argv contains only scriptname

Alecz added the comment: I ran into this issue by doing the following steps, though I did not try to reproduce: 1 - install Python 3.4 2 - have windows Always Open .py files with Python 3 - install Python 2.7 Then I encountered issues where all .py scripts were opened with Python 2.7. After s

[issue7936] sys.argv contains only scriptname

TonyP added the comment: I have v2.7, v3.2, and v3.3 installed on a Win7 64-bit machine and the exact same setup on a Win7 32-bit machine. The 32-bit works OK. The 64-bit machine had this argv problem, too! (I tried installing either Win32/Win64 version, no difference!) Adding %* fixed the

[issue7936] sys.argv contains only scriptname

Changes by Martin v. Löwis : -- versions: +Python 2.7, Python 3.1, Python 3.2, Python 3.3 -Python 2.6 ___ Python tracker ___ ___ Python

[issue7936] sys.argv contains only scriptname

Bill Hayes added the comment: I finally found a solution from a page on StackOverflow. I had to add the two characters %* to the end of the Data value for the Windows registry key: HKEY_CLASSES_ROOT\Applications\python.exe\shell\open\command So the Data value is now: "C:\Python26\python.ex

[issue7936] sys.argv contains only scriptname

Pierre Bourgault added the comment: I had the same problem with another version of python on Windows 7. We are using python 2.4.2 for production and it is installed in D:\Tools\Python. For experimentation purpose, I installed Python 2.7 in the usual location. It broke a few things and I unins

[issue7936] sys.argv contains only scriptname

Jiri Kulik added the comment: I'm sorry, I changed version to 3.3 by mistake. Did not want to do it. -- versions: +Python 3.1 -Python 3.3 ___ Python tracker ___ _

[issue7936] sys.argv contains only scriptname

Jiri Kulik added the comment: Encountered the same issue with 3.1.2 and 3.1.3 64bit on Win7 64bit. I was able to fix it in registry but did so many changes at once that I'm not able to reproduce (was really annoyed after trying to fix it for half a day...). Anyway, sending my observations: -

[issue7936] sys.argv contains only scriptname

Bill Hayes added the comment: I found this page while encountering the same problem (only one argument, the scriptname, being passed in from the command line), and wanted to post the following workaround. I'm running Vista and using Python 2.6. In summary I had to have 'python' at the beginni

[issue7936] sys.argv contains only scriptname

Tom Zych added the comment: The problem went away by itself after a while. I suspect a Windows update. -- ___ Python tracker ___ ___ P

[issue7936] sys.argv contains only scriptname

Sworddragon added the comment: I have now uninstalled Python 2 and 3 and installed them new. First Python 2 with only register extension and compile files to bytecode. After this I have made the same with Python 3. In the "Open with" menu was now "python" registered which was Python 3 (sys.ve

[issue7936] sys.argv contains only scriptname

Eric Smith added the comment: So the real question is is: how does that key get that invalid value? I can't reproduce the problem. I believe that key you mention is an alias for HKEY_CURRENT_USER\Software\Classes\Applications\python.exe\shell\open\command, which doesn't exist on my XP machin

[issue7936] sys.argv contains only scriptname

Sworddragon added the comment: Now I found the real solution (and don't forgot to set it to Python 3 back). I have searched in the registry for python.exe to look how Python 2 is doing this. I sawed a key that looks dissimilar to the others before. It is the key HKEY_USERS\S-1-5-21-1078081533

[issue7936] sys.argv contains only scriptname

Sworddragon added the comment: I made a mistake in the last post. After I have set the value, Python 2 was active and I forgot to set it to Python 3 back. This solution doesn't work. Well, I can't edit or delete the post. -- ___ Python tracker

[issue7936] sys.argv contains only scriptname

Sworddragon added the comment: I have set now the key to "E:\Python31\python.exe" "%%1" %%* and it works. So Windows XP need double % too. The installer of the next version should consider this. -- ___ Python tracker

[issue7936] sys.argv contains only scriptname

Sworddragon added the comment: This registry key contains "E:\Python31\python.exe" "%1" %*. I have too 2 python versions installed and manually associated the .py files to Python 3. -- ___ Python tracker _

[issue7936] sys.argv contains only scriptname

Eric Smith added the comment: That being said, it would be interesting to see what the registry key HKEY_CLASSES_ROOT\Python.File\shell\open\command contains. -- ___ Python tracker

[issue7936] sys.argv contains only scriptname

Eric Smith added the comment: I agree with Mark: there's probably nothing Python can do about this. It's almost certainly an error with how Python is being invoked. -- nosy: +eric.smith ___ Python tracker

[issue7936] sys.argv contains only scriptname

Mark Dickinson added the comment: >From various other sites, and from experiments (thanks Eric Smith) it looks >like the associations reported by 'assoc' and 'ftype' aren't necessarily the >associations that are actually being used. Sworddragon: can you get any useful information out of the

[issue7936] sys.argv contains only scriptname

Mark Dickinson added the comment: Here's a link to a similar discussion about Perl on Windows: http://community.activestate.com/forum-topic/problem-passing-arguments -- ___ Python tracker _

[issue7936] sys.argv contains only scriptname

Mark Dickinson added the comment: Closed issue 8984 as a duplicate of this; merging nosy lists. Tom, did you ever find a solution to this problem? -- nosy: +Sworddragon, loewis, mark.dickinson, merwok ___ Python tracker

[issue7936] sys.argv contains only scriptname

Tom Zych added the comment: No joy :( I tried putting double-quotes around %%*, that didn't work either. Tried single-quotes too, just in case it works like a Bourne-type shell. BTW I forgot to set 3.1 on my earlier message. That business about having to double the % rings a faint bell from

[issue7936] sys.argv contains only scriptname

Amaury Forgeot d'Arc added the comment: I've read on a random forum somewhere that % need to be doubled on Windows 7. Tom, can you try changing the association by typing FTYPE Python.File="C:\Python31\py31.exe" "%%1" %%* -- ___ Python tracker

[issue7936] sys.argv contains only scriptname

Tom Zych added the comment: I'm getting something like this on Windows 7: C:\>assoc .py .py=Python.File C:\>ftype Python.File Python.File="C:\Python31\py31.exe" "%1" %* C:\>args.py 1 2 3 Python version: sys.version_info(major=3, minor=1, micro=1, releaselevel='final', serial=0) Command-line

[issue7936] sys.argv contains only scriptname

JT Johnson added the comment: Sorry for a double-comment, but I thought of posting this after I already submitted the last one and I found no edit button. Here's some output: "Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\JT>asso

[issue7936] sys.argv contains only scriptname

JT Johnson added the comment: Actually, I was playing around with it and I found that using the "python" command before it does work. Now, when I type what you said to do, it shows that there is no association, even though i can run a program without the python command. This is quite strange..

[issue7936] sys.argv contains only scriptname

New submission from JT Johnson : I am running Python 2.6.4 on Windows Vista and when I try to get any command line arguments via sys.argv, it only contains sys.argv[0], but nothing else. Even if I supply several parameters. The only third-parts modules I am using are Pygame, but even before Py