
I'm using Windows XP SP2. Uninstalled 2.3, installed 2.4 (running as me, not as administrator). No problems so far. Tried installing pywin32-203.win32-py2.4.exe When I try to install it as me, it gets as far as "ready to install." When I click Next, it says Can't load Python for pre-install script and quits, even though earlier it said it had found Python 2.4 in the registry. When I try to install it as Administrator, it quits immediately, saying that it couldn't locate a Python 2.4 installation. My hypothesis: When I install 2.4 as me, it puts it in my user registry, not the system-wide registry, and then pywin32 can't find it. I'm going to unstall and try again as Administrator.

Follow-up: When I install Python as Administrator, all is well. In that case (but not when installing it as me), it asks whether I want to install it for all users or for myself only. I then install pywin32 and it works. So it may be that a caveat is in order to people who do not install 2.4 as Administrator.

Andrew Koenig wrote:
So it may be that a caveat is in order to people who do not install 2.4 as Administrator.
I think the trouble is not with 2.4, here - the trouble is with installing pywin32. As you said, the installation of Python itself went fine.
My hypothesis: When I install 2.4 as me, it puts it in my user registry, not the system-wide registry,
I can confirm this hypothesis. In a per-user installation, the registry settings are deliberately change for the user, not for the entire system. Otherwise, it wouldn't be per-user. Also, the user might not be able to write to the machine registry (unless he is a member of the Power Users group).
and then pywin32 can't find it.
That sounds likely, but I cannot confirm it. If it is, it is a bug in pywin32 (and, in turn, possibly in distutils). Regards, Martin

Follow-up: When I install Python as Administrator, all is well. In that case (but not when installing it as me), it asks whether I want to install it for all users or for myself only. I then install pywin32 and it works. So it may be that a caveat is in order to people who do not install 2.4 as Administrator.

Andrew Koenig wrote:
So it may be that a caveat is in order to people who do not install 2.4 as Administrator.
I think the trouble is not with 2.4, here - the trouble is with installing pywin32. As you said, the installation of Python itself went fine.
My hypothesis: When I install 2.4 as me, it puts it in my user registry, not the system-wide registry,
I can confirm this hypothesis. In a per-user installation, the registry settings are deliberately change for the user, not for the entire system. Otherwise, it wouldn't be per-user. Also, the user might not be able to write to the machine registry (unless he is a member of the Power Users group).
and then pywin32 can't find it.
That sounds likely, but I cannot confirm it. If it is, it is a bug in pywin32 (and, in turn, possibly in distutils). Regards, Martin
participants (4)
-
"Martin v. Löwis"
-
Andrew Koenig
-
Andrew Koenig
-
Thomas Heller