On 10/29/07, Mark Hammond <mhammond@skippinet.com.au> wrote:
This will be related to the registry entries being written into the 32bit part of the registry rather than the 64bit version. As a result, whenever Python is embedded in another application and needs to use the registry to locate its installation path, it fails, and uses the fallback relative values of ".\DLLs", ".\lib" etc. On the other hand, when Python is started normally, it can locate its library automatically, so the correct entries are used.
If you search the python-dev archives, you will see a discussion on this issue, and also a new copy of the installer put together by Martin V Loewis to test the fix for this issue. It is expected that the fix will also appear in Python 2.5.2.
Hope this helps,
Thanks, Mark.
The mail thread at http://mail.python.org/pipermail/python-dev/2007-July/073900.html describes the problem and points to a fixed installer. In short, the official Python 2.5.1 amd64 installer sets the 'reflected' registry keys at HKLM\Software\Wow6432node\Python, instead of HKLM\Software\Python.
I installed Martin v. Löwis's private build and that fixed my problems.
/George V. Reilly http://www.georgevreilly.com/blog