Re: Command-line does work when scheduled
- From: "Gabriel Genellina" <gagsl-py2@xxxxxxxxxxxx>
- Date: Sat, 29 Sep 2007 23:45:59 -0300
En Sat, 29 Sep 2007 22:04:06 -0300, Jim <jscrerar@xxxxxxxxxxxxxx> escribi�:
If it works this way, maybe the .py file extension is not correctly
registered.
Yes, it works this way.
How do I register the .py extension correctly?
From a command line, type:
assoc .py
You should get:
..py=Python.File
If you get an error, or another thing like py_auto_file:
assoc .py=Python.File
Then:
ftype Python.File
You should get:
Python.File=c:\path\to\python.exe "%1" %*
If you don't:
ftype Python.File=c:\path\to\python.exe "%1" %*
The %* at the end is important: if you created the association by using "Open with...", or selecting Python from the list of installed programs, very likely the command says only "%1" - that is, the script being open, but without any additional arguments.
Better if you have administrative rights to do this tasks.
--
Gabriel Genellina
.
- Follow-Ups:
- References:
- Command-line does work when scheduled
- From: Jim
- Re: Command-line does work when scheduled
- From: Gabriel Genellina
- Re: Command-line does work when scheduled
- From: Jim
- Re: Command-line does work when scheduled
- From: Gabriel Genellina
- Re: Command-line does work when scheduled
- From: Jim
- Command-line does work when scheduled
- Prev by Date: earn $26800 a month with google adsense
- Next by Date: OSDC 2007 earlybird registration now open!
- Previous by thread: Re: Command-line does work when scheduled
- Next by thread: Re: Command-line does work when scheduled
- Index(es):
Relevant Pages
|