Because if that registry entry is not added and the user has no other python, 
then they would not be able to run LilyPond's python scripts.

--
Phil Holmes


  ----- Original Message ----- 
  From: Frederick Bartlett 
  To: Phil Holmes 
  Cc: lilypond-user@gnu.org 
  Sent: Thursday, September 12, 2013 3:56 PM
  Subject: Re: Windows registry, Python, and LilyPond


  Well, yes ... but why would I want LilyPond's python to run a script instead 
of the system's python?


  Perhaps I'm just not advanced enough a LilyPond user ....


  Fred




  On 12 September 2013 10:22, Phil Holmes <m...@philholmes.net> wrote:

    I believe it allows you to type progname.py at the command line, and have 
LilyPond's python run the script.

    --
    Phil Holmes


      ----- Original Message ----- 
      From: Frederick Bartlett 
      To: Phil Holmes 
      Cc: lilypond-user@gnu.org 
      Sent: Thursday, September 12, 2013 3:16 PM
      Subject: Re: Windows registry, Python, and LilyPond


      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.


      This seems, if anything, weirder than my last message. It's clearly a 
Windows problem ... I'm just hoping a LilyPonder will be able to explain the 
function of the LilyPond python registry key.

      Thanks again!
      Fred




      On 12 September 2013 10:09, Phil Holmes <m...@philholmes.net> wrote:

        Which LilyPond version?

        --
        Phil Holmes


          ----- Original Message ----- 
          From: Frederick Bartlett 
          To: lilypond-user@gnu.org 
          Sent: Thursday, September 12, 2013 2:32 PM
          Subject: Windows registry, Python, and LilyPond


          All,


          I just installed LilyPond on a new laptop (same OS -- Windows 7 -- as 
before), but this time the registry entry 
HKCR\Python\shell\open\command\(Default), which is set to C:\Program 
Files\LilyPond\usr\bin\python.exe ...., interferes with my path to my Python 
installation in C:\Python27.


          There seem to have been problems regarding the registry in the past, 
but not exactly like the one I've encountered ... does anyone have handy info 
on how to convince Windows to let LilyPond run its own python while everything 
else runs my python?

          Thanks!

          Fred


          -- 

          “To my knowledge I have no knowledge.” -- John Kerry, the Secretary 
of State of the United States of America, in response to Senator Barbara Boxer, 
3 Sep 2013



----------------------------------------------------------------------


          _______________________________________________
          lilypond-user mailing list
          lilypond-user@gnu.org
          https://lists.gnu.org/mailman/listinfo/lilypond-user





      -- 

      “To my knowledge I have no knowledge.” -- John Kerry, the Secretary of 
State of the United States of America, in response to Senator Barbara Boxer, 3 
Sep 2013




  -- 

  “To my knowledge I have no knowledge.” -- John Kerry, the Secretary of State 
of the United States of America, in response to Senator Barbara Boxer, 3 Sep 
2013
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to