Python, Windows, and Cygwin

[Ben Scott]

On Mon, Mar 16, 2009 at 11:08 AM, Paul Lussier <p.lussier at comcast.net> wrote:
>> For what it's worth, if you just associate .py files with a Python
>> installation in C:\Python via the standard Windows mechanism for
>> specifying what application loads a particular extension ...
>
> You assume I have a clue to what you're talking about :)

  Windows has a mechanism where double-clicking a file will open the
right program for that file extension (file type).  Kind of like
/etc/mime.types and /etc/mime.cap do on Unix, except it's at a lower
layer in the OS on 'doze.

  GUI method: Open up a Windows Explorer window ("My Computer" will
do).  In the menu bar, in the "Tools" menu, open "Folder Options".
Tab "File Types".

  CLI method: The command is "ASSOC".  "ASSOC /?" will get one started.

> Also, given that I want to be able to ssh into the windows system and
> exec a python script directly, will that make a difference ?

  I believe it will make a difference.  I don't think Cygwin knows or
cares about Windows file extension mappings.  (Then again, it's been
years and years since I touched Cygwin.  My memory could be bad or the
software could have evolved or I might have missed a feature.)

  Also, this Windows file association stuff *requires* your Python
scripts to end in ".py".  If you've got scripts that don't end in
".py" and want them to still work, it won't unless your Cygwin
Unix-ish paths are happy.

-- Ben