making a python program in windows

[rustom]

On May 21, 5:09 pm, Duncan Booth <duncan.bo... at invalid.invalid> wrote:
> rustom <rustompm... at gmail.com> 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 question about the file association is one you have to answer
> for yourself. When you install Python it associates .pyw with pythonw and
> .py with python. If something on your system has changed this the best
> thing you can do is to change it back.
>
> Try typing the following commands and then fixing any differences by typing
> the expected output as the command parameter
> (e.g. "assoc .py=Python.File"):
>
> C:\>assoc .py
> .py=Python.File
>
> C:\>assoc .pyw
> .pyw=Python.NoConFile
>
> C:\>ftype Python.file
> Python.file="C:\Python26\python.exe" "%1" %*
>
> C:\>ftype Python.NoConFile
> Python.NoConFile="C:\Python26\pythonw.exe" "%1" %*
>
> --
> Duncan Boothhttp://kupuguy.blogspot.com

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?