This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Windows Registry issue with 2.5.2 AMD64 msi
Type: Stage:
Components: Installation Versions: Python 2.5
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: brian.curtin, iggyboo, loewis
Priority: normal Keywords:

Created on 2008-04-03 02:16 by iggyboo, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg64887 - (view) Author: Jason (iggyboo) Date: 2008-04-03 02:16
I have tried multiple times and even checking manually, but the
Python 2.5.2 AMD64 msi installer does not register Python correctly, or
it doesn't enter it into the registry correctly.  I'm not sure.  I
install it after uninstalling 2.5.1 and and when I try to install
wxPython2.8 and pygtk-2.10.6 both give me an error that they cannot find
Python or its path in the registry.  I reinstall 2.5.1 and it all works
perfectly.  I'm using all default selections and just clicking
"Next,Next,Next, etc."
msg64891 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2008-04-03 07:01
Do you perform a per-user or per-machine installation?

When you look at the Python registry keys, which ones get written?
msg64914 - (view) Author: Jason (iggyboo) Date: 2008-04-04 05:17
I did a per-machine installation (Install for all users).  I don't have 
the registry information at the moment, but I'll do some more 
uninstalling and reinstalling and get that information to you.

Martin v. Löwis wrote:
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
> Do you perform a per-user or per-machine installation?
>
> When you look at the Python registry keys, which ones get written?
>
> ----------
> nosy: +loewis
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue2539>
> __________________________________
>
msg97394 - (view) Author: Brian Curtin (brian.curtin) * (Python committer) Date: 2010-01-08 04:25
It seems like this may have been the result of registry redirection. Jason didn't say if the 2.5.1 install he went back to was 64-bit or not, but that could have been the difference. Given how old this is, I doubt he remembers :)

wxPython has 32 and 64 bit versions, so if you have a 64-bit Python and try to install the 32-bit wx, the wx installer won't immediately find a registry entry. It will be redirected to HKLM\Software\Wow6432Node\Python, which won't exist.

I think we can close this. Any thoughts, Martin?
msg97396 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2010-01-08 08:54
Whatever the problem, it seems to have gone away. Closing as out-of-date.
History
Date User Action Args
2022-04-11 14:56:32adminsetgithub: 46791
2010-01-08 08:54:11loewissetstatus: open -> closed
resolution: out of date
messages: + msg97396
2010-01-08 04:25:52brian.curtinsetnosy: + brian.curtin
messages: + msg97394
2008-04-04 05:17:21iggyboosetmessages: + msg64914
2008-04-03 07:01:39loewissetnosy: + loewis
messages: + msg64891
2008-04-03 02:16:25iggyboocreate