New submission from Jason R. Coombs <jar...@jaraco.com>: It appears as if bdist_msi isn't properly tagging 64-bit binary builds.
When launching an .msi built by Python 2.6.2 using bdist_msi, such as numpy found here (https://sourceforge.net/project/showfiles.php?group_id=1369&package_id=175103), it improperly detects the location of Python (which it gets from the registry). If the 32-bit Python 2.6 is also installed, it finds that version. If 32-bit Python 2.6 is not installed, it fails to find the Python installation. Even if the proper 64-bit Python 2.6 location is selected, the files are not installed to the Python 2.6 site-packages. Furthermore, the registry Uninstall information is stored in the Wow6432Node. bdist_wininst executables appear to detect 64-bit Python and install correctly. I will attempt to recreate this problem with a minimal project and clean 64-bit Vista or Windows 7 machine at a later date. ---------- assignee: tarek components: Distutils messages: 89221 nosy: jaraco, tarek severity: normal status: open title: distributions built with bdist_msi on 64-bit Windows fail to install correctly versions: Python 2.6 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6258> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
