Re: Command line arguments on Vista
Thanks for the answers; that was the problem exactly. --JMike Duncan Booth wrote: It sounds like the registry entry for running Python files is messed up. Can you go to a command line and see what the command 'ftype Python.File' displays? (Assuming that command lines and ftype still work on Vista) The output should be: Python.File=C:\Python25\python.exe %1 %* but if it only says: Python.File=C:\Python25\python.exe %1 then you would get the behaviour you observed (on any version of Windows, not just Vista). -- http://mail.python.org/mailman/listinfo/python-list
Re: Command line arguments on Vista
Duncan Booth [EMAIL PROTECTED] escribió en el mensaje news:[EMAIL PROTECTED] It sounds like the registry entry for running Python files is messed up. Can you go to a command line and see what the command 'ftype Python.File' displays? (Assuming that command lines and ftype still work on Vista) The output should be: Python.File=C:\Python25\python.exe %1 %* but if it only says: Python.File=C:\Python25\python.exe %1 then you would get the behaviour you observed (on any version of Windows, not just Vista). That would happen if the association was not made by the Python installer, but by the user selecting Python.exe the first time he tried to execute a Python script by double-clicking on it. -- Gabriel Genellina -- http://mail.python.org/mailman/listinfo/python-list
Re: Command line arguments on Vista
By the way, note that if I say (on Vista) python printargs.py booga -a wooga I get the desired output: there are 4 args arg: printargs.py arg: booga arg: -a arg: wooga So the quesiton still stands, what's up with that? Thanks, --JMike -- http://mail.python.org/mailman/listinfo/python-list
Re: Command line arguments on Vista
Some further information: perl seems to do the same thing (losing arguments). We think it may have something to do with file association. Any ideas anyone? --JMike -- http://mail.python.org/mailman/listinfo/python-list
Re: Command line arguments on Vista
[EMAIL PROTECTED] wrote: But on Windows Vista, when I run that command, I get there are 1 args arg: printargs.py What's up with that? It sounds like the registry entry for running Python files is messed up. Can you go to a command line and see what the command 'ftype Python.File' displays? (Assuming that command lines and ftype still work on Vista) The output should be: Python.File=C:\Python25\python.exe %1 %* but if it only says: Python.File=C:\Python25\python.exe %1 then you would get the behaviour you observed (on any version of Windows, not just Vista). -- http://mail.python.org/mailman/listinfo/python-list