Author pje
Recipients carwyn, erluk, loewis, pje, srid, ssbarnea, tarek
Date 2009-12-28.01:56:12
SpamBayes Score 8.77473e-07
Marked as misclassified No
Message-id <1261965375.49.0.84145297889.issue6792@psf.upfronthosting.co.za>
In-reply-to
Content
ISTM there may be two ways to fix this problem; one was to change the
.exe header produced by bdist_wininst, but in retrospect, it can't fix
this because it's likely Windows' 64-to-32 bit conversion (Wow6432Node)
that's changing the registry path used, rather than anything that Python
or distutils is doing.

The other way, which has more probability of working, is for the 64-bit
Python installer to include an extra registry entry that would allow the
32 bit versions to find the 64-bit version.

(This might also require an install-time 64/32 compatibility check being
added to the .exe header for bdist_wininst to prevent installing
binary-incompatible extensions.)
History
Date User Action Args
2009-12-28 01:56:15pjesetrecipients: + pje, loewis, tarek, carwyn, ssbarnea, srid, erluk
2009-12-28 01:56:15pjesetmessageid: <1261965375.49.0.84145297889.issue6792@psf.upfronthosting.co.za>
2009-12-28 01:56:13pjelinkissue6792 messages
2009-12-28 01:56:12pjecreate