[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Windows registry, Python, and LilyPond
From: |
Tim Roberts |
Subject: |
Re: Windows registry, Python, and LilyPond |
Date: |
Thu, 12 Sep 2013 10:05:20 -0700 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 |
Frederick Bartlett <address@hidden> wrote:
>
>
> Oh, sorry! 2.16.2
>
> I have since found that I can run python scripts from the command line
> by typing, say,
> python myscript.py
>
> While just typing
> myscript
> produces an error, even though the Windows file association has been
> set to c:\Python27\python.exe.
The file association lets you type
myscript.py
If you want to be able to type "myscript", you need to add .py to the
list of "automatic" extensions. That is stored in the PATHEXT
environment variable:
set PATHEXT=%PATHEXT%;.py;.pyw
--
Tim Roberts, address@hidden
Providenza & Boekelheide, Inc.
- Windows registry, Python, and LilyPond, Frederick Bartlett, 2013/09/12
- Re: Windows registry, Python, and LilyPond, Phil Holmes, 2013/09/12
- Re: Windows registry, Python, and LilyPond, Frederick Bartlett, 2013/09/12
- Re: Windows registry, Python, and LilyPond, Phil Holmes, 2013/09/12
- Re: Windows registry, Python, and LilyPond, Frederick Bartlett, 2013/09/12
- Re: Windows registry, Python, and LilyPond, Phil Holmes, 2013/09/12
Re: Windows registry, Python, and LilyPond, Hilary Snaden, 2013/09/12
- Re: Windows registry, Python, and LilyPond,
Tim Roberts <=
- Re: Windows registry, Python, and LilyPond, Frederick Bartlett, 2013/09/13
- Re: Windows registry, Python, and LilyPond, Frederick Bartlett, 2013/09/15