rustom wrote:
>
>Thanks for this (and all other) tips.
>Strangely now my m/c shows things exactly like so. A new .py file gets
>associated with python but two days ago it was with pythonw?!
No, .py files are always associated with python.exe. .pyw files are
associated with pythonw.exe.
--
Tim R
Tim Roberts wrote:
Dave Angel wrote:
Anyway, now you can see two batch files you could use to make a
particular version of Python active. The first one uses assoc and ftype
to fix the asssociations. And the other changes the environment variable
PATHEXT to make the extension optional. No
rustom wrote:
Thanks for this (and all other) tips.
Strangely now my m/c shows things exactly like so. A new .py file gets
associated with python but two days ago it was with pythonw?!
Any recos on where I could read up on this stuff?
I by "all this stuff" you mean: Windows file associations,
t
On May 21, 5:09 pm, Duncan Booth wrote:
> rustom wrote:
> > i suppose the question is entirely about setting properly (and
> > grokking) file associations -- why is a .py file associated with
> > pythonw and not python? And is making this association right enough to
> > make a .py file in windows
Dave Angel wrote:
>
>Anyway, now you can see two batch files you could use to make a
>particular version of Python active. The first one uses assoc and ftype
>to fix the asssociations. And the other changes the environment variable
>PATHEXT to make the extension optional. Note that changing t
Rustom Mody wrote:
I know how to make a python script behave like a (standalone) program
in unix --
1. put a #! path/to/python as the first line
2. make the file executable
The closest I know how to do this in windows is:
r-click the file in win-explorer
goto properties
goto open with
change p
rustom wrote:
> i suppose the question is entirely about setting properly (and
> grokking) file associations -- why is a .py file associated with
> pythonw and not python? And is making this association right enough to
> make a .py file in windows behave like a shebang file in unix?
I think the
Rustom Mody wrote:
I know how to make a python script behave like a (standalone) program
in unix --
1. put a #! path/to/python as the first line
2. make the file executable
The closest I know how to do this in windows is:
r-click the file in win-explorer
goto properties
goto open with
change pyt
On May 21, 3:19 pm, "Martin P. Hellwig"
wrote:
> Rustom Mody wrote:
> > I know how to make a python script behave like a (standalone) program
> > in unix --
> > 1. put a #! path/to/python as the first line
> > 2. make the file executable
>
> > The closest I know how to do this in windows is:
> > r
Rustom Mody wrote:
I know how to make a python script behave like a (standalone) program
in unix --
1. put a #! path/to/python as the first line
2. make the file executable
The closest I know how to do this in windows is:
r-click the file in win-explorer
goto properties
goto open with
change pyt
I know how to make a python script behave like a (standalone) program
in unix --
1. put a #! path/to/python as the first line
2. make the file executable
The closest I know how to do this in windows is:
r-click the file in win-explorer
goto properties
goto open with
change pythonw to python
Can s
11 matches
Mail list logo
