[pygtk] problem installing PyGTK on a clean WinXP system

[John Pye]

Brad Schick wrote:
> John Pye wrote:
>   
>> Are you saying that on your copy of Windows, Python has added itself to
>> your PATH?
>>   
>>     
> I test this on a fresh vmware instance on my side, and you are
> correct... python is not in the system path. But interestingly, the
> c:\python25\ directory also does *not* include msvcr71.dll. I used this
> installer:
>
> http://www.python.org/ftp/python/2.5.1/python-2.5.1.msi
>   

That is the same Python installer as I'm using. But I found I did have
the msvcr71.dll. Perhaps on your VM you have done a Windows Update, and
consequently you already have msvcr71.dll in your system32 directory,
and consequently Python didn't install it to c:\Python25? Possibly?

> Something else like maybe the pywin32 stuff must be installing it. So it
> seems likely that the pyxxxx.exe installers just don't work on a fresh
> non-updated WinXP system. I think that leaves you with one option;
> include msvcr71.dll in your installer and extract it to the same temp
> directory used to save and run the pyxxxx.exe installers.
>   

Isn't it an option to rebuild the Py* installers?

If my assumption about msvcr71.dll above is correct, then the solution
is for me to set the PATH (add c:\Python25 or whatever) before
attempting to run the Py* installers. Alternatively, I can temporarily
set the AppPaths for each installer. So if I can assume that msvrt71
will always be available somewhere (once Python is installer), I
shouldn't need to provide my own copy.

There is another issue with the Py* installers, which is that (AFAICT)
they can't be run in 'silent' mode, which (I presume) makes the 'all in
one' PyGTK installer, and my ASCEND installer both rather more verbose
than they need to be.

Cheers
JP