Re: The status of the generated .nsi install script

2009-09-03 Thread Ville M. Vainio
On Thu, Sep 3, 2009 at 9:27 PM, Edward K. Ream wrote: > Mystery solved: forgot to double the backslashes in the Python triple > string. Remember that you can r""" Make triple quoted raw strings too """ -- Ville M. Vainio http://tinyurl.com/vainio --~--~-~--~~~--

Re: The status of the generated .nsi install script

2009-09-03 Thread Edward K. Ream
On Sep 3, 1:08 pm, "Edward K. Ream" wrote: > On Thu, Sep 3, 2009 at 12:55 PM, Rob Sheppard wrote: > > > Edward K. Ream wrote: > > > > The following is not working for me: > > > > ReadRegStr $9 HKLM "SOFTWARE\Python\PythonCore\2.6\InstallPath" "" Mystery solved: forgot to double the backslashe

Re: The status of the generated .nsi install script

2009-09-03 Thread Edward K. Ream
On Thu, Sep 3, 2009 at 12:55 PM, Rob Sheppard wrote: > > Edward K. Ream wrote: > > > > The following is not working for me: > > > > ReadRegStr $9 HKLM "SOFTWARE\Python\PythonCore\2.6\InstallPath" "" > > > > That is, $9 is always empty, even though the registry does have an > > InstallPath entry.

Re: The status of the generated .nsi install script

2009-09-03 Thread Rob Sheppard
Edward K. Ream wrote: > > The following is not working for me: > > ReadRegStr $9 HKLM "SOFTWARE\Python\PythonCore\2.6\InstallPath" "" > > That is, $9 is always empty, even though the registry does have an > InstallPath entry. > > Probably something simple, but I'm stuck. Any ideas? > > Edward >

Re: The status of the generated .nsi install script

2009-09-03 Thread Edward K. Ream
On Thu, Sep 3, 2009 at 12:06 PM, Rob Sheppard wrote: > > Oh, I was under the impression you wanted to support 2.3 or later. > Actually, I'm not sure why I was thinking that, but I'm guessing I read > it in the docs. > Leo only works for 2.5 and 2.6. > > > Anyone see any problems with this appro

Re: The status of the generated .nsi install script

2009-09-03 Thread Rob Sheppard
Edward K. Ream wrote: > At present, the only two valid Pythons are > 2.5 and 2.6 > Oh, I was under the impression you wanted to support 2.3 or later. Actually, I'm not sure why I was thinking that, but I'm guessing I read it in the docs. > Anyone see any problems with this approach? > >

The status of the generated .nsi install script

2009-09-03 Thread Edward K. Ream
At present, the only remaining item to do for the installer is to determine the location of Python. This is what the now- disabled .onInit function does. On my machine, regedit contains entries for all all my Python folders. For example: HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\2.5 HKEY_L