I'm using Windows 7 (x64) and Python 2.6.2.
The Python 2.6 installer does add information to the registry, though the other installers can't seem to find it. This tool returns no error, and also succesfully edits the registry, though it doesn't solve my problem.
Perhaps there's a change in how Python (and the windows installers) behave in the new operating system. Anyone have any ideas?
I'd love to hear from you at effbot-public{at}piratesofpacifica{dto}.com
The (64bit) MSI installer for Python 2.6.2 DOES correctly place the information in the registry. The problem is that the installer packages for extensions are 32bit, and their calls for the registry data are virtualized and are redirected to HKLM/Software/Wow6432Node/Python/... instead of HKLM/Software/Python/...
I was able to use the 32bit installer for PIL by duplicating the Python registry key to the HKLM/Software/Wow6432Node key.
Thank you very much for your script and the various comments.
I also got this Error Message Felix posted
...
if QueryValue(reg, installkey) == installpath :
WindowsError: [Errno 2] The system cannot find the file specified
...
Posted by Felix (2007-01-28)
(... and doing it the way Mark suggested created some registry entries at other locations than my ordinary (properly self registering) python installations.)
For me the solution was simply to run the python interpreter with the script (the initial version with "version = sys.version[:3]") AS ADMINISTRATOR.
Didn't work for me.
I'm using Windows 7 (x64) and Python 2.6.2.
The Python 2.6 installer does add information to the registry, though the other installers can't seem to find it. This tool returns no error, and also succesfully edits the registry, though it doesn't solve my problem.
Perhaps there's a change in how Python (and the windows installers) behave in the new operating system. Anyone have any ideas?
I'd love to hear from you at effbot-public{at}piratesofpacifica{dto}.com
I've found the problem.
The (64bit) MSI installer for Python 2.6.2 DOES correctly place the information in the registry. The problem is that the installer packages for extensions are 32bit, and their calls for the registry data are virtualized and are redirected to HKLM/Software/Wow6432Node/Python/... instead of HKLM/Software/Python/...
I was able to use the 32bit installer for PIL by duplicating the Python registry key to the HKLM/Software/Wow6432Node key.
Had the same problem and was just about to lose hope. Tried this and it worked. You are my hero! Thank you so much! :)
Thank you very much for your script and the various comments.
I also got this Error Message Felix posted
...
if QueryValue(reg, installkey) == installpath :
WindowsError: [Errno 2] The system cannot find the file specified
...
Posted by Felix (2007-01-28)
(... and doing it the way Mark suggested created some registry entries at other locations than my ordinary (properly self registering) python installations.)
For me the solution was simply to run the python interpreter with the script (the initial version with "version = sys.version[:3]") AS ADMINISTRATOR.