[issue23120] installation order of 32bit and 64bit python seems to matter

[Zachary Ware]

Change by Zachary Ware :


--
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23120] installation order of 32bit and 64bit python seems to matter

[Peter Santoro]

New submission from Peter Santoro:

It appears that installation order matters when installing both 32bit and 64bit 
versions of Python.  If you install the 32bit version first, the 64bit version 
will uninstall the 32bit version.  Here are the steps I used:

1. Starting point (Windows 7 64bit with latest MS patches):
   Python 3.3.5 32bit (c:\bin32\python33, required for support of older systems 
that will be upgraded to 3.4.3 when it's available)
   Python 3.4.1 32bit (c:\bin32\python34)
   Python 3.4.1 64bit (c:\bin\python34, included in PATH)
2. Uninstalled
   Python 3.4.1 32bit - ran as expected
   Python 3.4.1 64bit - ran as expected
3. Attempted Install (32bit install before 64bit install)
   Python 3.4.2 32bit (c:\bin32\python34) - ran as expected
   Python 3.4.2 64bit (c:\bin\python34) - install dialog had red warning 
message at top stating that previous version will be uninstalled; if you 
continue, the 64bit install deletes the Python 3.4.2 32bit install
4. Work around installation order (64bit install before 32bit install):
   Python 3.4.2 64bit (c:\bin\python34) - ran as expected
   Python 3.4.2 32bit (c:\bin32\python34) - ran as expected

Notes:

I've reported other strange issues with multiple versions of python installed, 
but they were deemed different than the original reported bug and were not 
further discussed.  It's quite possible that the combination of python versions 
installed/uninstalled over time on this system has caused some 
bad/unexpected/untested state (e.g. Windows registry entries).

--
components: Installation
messages: 233131
nosy: pe...@psantoro.net
priority: normal
severity: normal
status: open
title: installation order of 32bit and 64bit python seems to matter
type: behavior
versions: Python 3.4

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23120
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23120] installation order of 32bit and 64bit python seems to matter

[Tim Golden]

Changes by Tim Golden m...@timgolden.me.uk:


--
components: +Windows
nosy: +steve.dower, tim.golden, zach.ware

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23120
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue23120] installation order of 32bit and 64bit python seems to matter

[Steve Dower]

Steve Dower added the comment:

I'm already quite keen to rename the registry key for 32-bit on Windows, since 
there are some places where that will cause conflicts. This won't be done for 
3.4 though, as we don't have an active maintainer for the old installer (Martin 
is still building them, but not working on it). I haven't yet thought about how 
the updated keys should look, but when I get time to get back to the installer 
I'll try some things.

The 3.5 installer shouldn't have this issue as it will use product codes to 
detect other Python installations rather than registry keys.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23120
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com