Christian Heimes schrieb:

Thomas Heller wrote:

...

Is it intended that python30.dll and python26.dll are not longer installed in the \windows\system32 directory?

This (pythonxy.dll not on $PATH) causes problems for COM objects implemented in Python.

How did you install Python 2.6? Did you install it only for yourself or for all users?

For all users. I only deselected the 'register file extensions' option. This is on XP SP3, with admin rights. -- Thanks, Thomas

2008/10/8 "Martin v. Löwis" :

Thomas Heller wrote:

...

Is it intended that python30.dll and python26.dll are not longer installed in the \windows\system32 directory?

No, it's not. Please create a bug report (or, better, study the msiexec logs, and msi.py, to find out why this happens).

I might not have time to look into this before the next release candidate.

I confirm this. The following lines in msi.py seem to be the cause of the change: #dlldir = PyDirectory(db, cab, root, srcdir, "DLLDIR", ".") #install python30.dll into root dir for now dlldir = root They were added by r61109: " Bundle msvcr90.dll as a "private assembly". " but I don't know if simply restoring the previous value will work in every case: If the C Run-Time is installed "privately", then python26.dll must stay in c:\python26. -- Amaury Forgeot d'Arc

I confirm this. The following lines in msi.py seem to be the cause of the change:

#dlldir = PyDirectory(db, cab, root, srcdir, "DLLDIR", ".") #install python30.dll into root dir for now dlldir = root

They were added by r61109: " Bundle msvcr90.dll as a "private assembly". " but I don't know if simply restoring the previous value will work in every case: If the C Run-Time is installed "privately", then python26.dll must stay in c:\python26.

Ah, ok. Maybe I can find some time next week to look into this, but I wouldn't mind if anybody else did. In any case, thanks for this research so far (and too bad that nobody noticed throughout all the beta releases). Regards, Martin