Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Windows Registry issue with 2.5.2 AMD64 msi #46791

Closed
iggyboo mannequin opened this issue Apr 3, 2008 · 5 comments
Closed

Windows Registry issue with 2.5.2 AMD64 msi #46791

iggyboo mannequin opened this issue Apr 3, 2008 · 5 comments
Labels
topic-installation

Comments

@iggyboo
Copy link
Mannequin

iggyboo mannequin commented Apr 3, 2008

BPO 2539
Nosy @loewis, @briancurtin

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2010-01-08.08:54:11.451>
created_at = <Date 2008-04-03.02:16:25.317>
labels = ['expert-installation']
title = 'Windows Registry issue with 2.5.2 AMD64 msi'
updated_at = <Date 2010-01-08.08:54:11.450>
user = 'https://bugs.python.org/iggyboo'

bugs.python.org fields:

activity = <Date 2010-01-08.08:54:11.450>
actor = 'loewis'
assignee = 'none'
closed = True
closed_date = <Date 2010-01-08.08:54:11.451>
closer = 'loewis'
components = ['Installation']
creation = <Date 2008-04-03.02:16:25.317>
creator = 'iggyboo'
dependencies = []
files = []
hgrepos = []
issue_num = 2539
keywords = []
message_count = 5.0
messages = ['64887', '64891', '64914', '97394', '97396']
nosy_count = 3.0
nosy_names = ['loewis', 'iggyboo', 'brian.curtin']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue2539'
versions = ['Python 2.5']
@iggyboo
Copy link
Mannequin Author

iggyboo mannequin commented Apr 3, 2008

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."

@iggyboo iggyboo mannequin added the topic-installation label Apr 3, 2008
@loewis
Copy link
Mannequin

loewis mannequin commented Apr 3, 2008

Do you perform a per-user or per-machine installation?

When you look at the Python registry keys, which ones get written?

@iggyboo
Copy link
Mannequin Author

iggyboo mannequin commented Apr 4, 2008

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\>

@briancurtin
Copy link
Member

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?

@loewis
Copy link
Mannequin

loewis mannequin commented Jan 8, 2010

Whatever the problem, it seems to have gone away. Closing as out-of-date.

@loewis loewis mannequin closed this as completed Jan 8, 2010
@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic-installation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@briancurtin