Re: Command Line Inputs from Windows

2015-01-05 Thread James Scholes
Chris Angelico wrote: > The latter form is governed by the association. I don't know off-hand > where that's set in the registry, but you should be able to poke > around in folder settings to find it (but, thank you very much > Microsoft, the exact menu path has changed a number of times between >

Re: Command Line Inputs from Windows

2015-01-03 Thread Gisle Vanem
Ken Stewart wrote: Here is a sample key: S1-5-21-1560217580-722697556-320042093-1000-Classes py_auto_file shell open command The corrected data for the key looks like this: "C:\Python34\python.exe" %1 %* Yikes! You use the awful cmd.exe as the shell d

Re: Command Line Inputs from Windows

2015-01-03 Thread Mark Lawrence
On 03/01/2015 08:03, Ken Stewart wrote: At the moment it looks like the Python installer didn't create these registry entries properly in Windows 7. If that is actally the case please raise an issue on the bug tracker at bugs.python.org if one doesn't already exist. -- My fellow Pythonistas

Re: Command Line Inputs from Windows

2015-01-03 Thread Chris Angelico
On Sat, Jan 3, 2015 at 7:03 PM, Ken Stewart wrote: > I used the 'find' tool in regedit to search for python in the registry. > There were many hits on the word python but only a handful had data fields > similar to the one above. Every instance was missing the %* string. I > modified them all.

Re: Command Line Inputs from Windows

2015-01-03 Thread Ken Stewart
Chris, Dennis, James, and Mark: SUCCESS! Thanks for your suggestions. It was the registry. Kudos to Dennis. The data strings for a lot of different "command" keys in the registry were missing the %* (percent star) characters. Thanks Chris for the explanation on why the %* string is needed

Re: Command Line Inputs from Windows

2015-01-03 Thread Mark Lawrence
On 02/01/2015 19:44, Ken Stewart wrote: Court of King Arthur, Court of BDFL actually. I’d appreciate any help you can provide. I’m having problems passing command line parameters from Windows 7 into a Python script (using Python 3.4.2). It works correctly when I call the interpreter explic

Re: Command Line Inputs from Windows

2015-01-02 Thread Mark Lawrence
On 02/01/2015 21:29, Chris Angelico wrote: On Sat, Jan 3, 2015 at 6:44 AM, Ken Stewart wrote: This works: I may have some details wrong, and it's likely to be a little different on Win7, but poke around and look for a missing %*. Or, better still, make sure you have the py.exe launcher; then

Re: Command Line Inputs from Windows

2015-01-02 Thread Chris Angelico
On Sat, Jan 3, 2015 at 2:41 PM, James Scholes wrote: > Chris Angelico wrote: >> The latter form is governed by the association. I don't know off-hand >> where that's set in the registry, but you should be able to poke >> around in folder settings to find it (but, thank you very much >> Microsoft,

Re: Command Line Inputs from Windows

2015-01-02 Thread Chris Angelico
On Sat, Jan 3, 2015 at 6:44 AM, Ken Stewart wrote: > This works: > python myScript.py arg1 arg2 arg3 > > This doesn’t work: > myScript.py arg1 arg2 arg3 The latter form is governed by the association. I don't know off-hand where that's set in the registry, but you should be able to poke around in

Command Line Inputs from Windows

2015-01-02 Thread Ken Stewart
Court of King Arthur, I’d appreciate any help you can provide. I’m having problems passing command line parameters from Windows 7 into a Python script (using Python 3.4.2). It works correctly when I call the interpreter explicitly from the Windows command prompt, but it doesn’t work when I e