Message89221
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. |
|
Date |
User |
Action |
Args |
2009-06-10 18:10:45 | jaraco | set | recipients:
+ jaraco, tarek |
2009-06-10 18:10:45 | jaraco | set | messageid: <1244657445.76.0.468429726834.issue6258@psf.upfronthosting.co.za> |
2009-06-10 18:10:43 | jaraco | link | issue6258 messages |
2009-06-10 18:10:43 | jaraco | create | |
|