This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients benjamin.peterson, lemburg, loewis, srid, tarek, zart
Date 2010-06-21.11:39:50
SpamBayes Score 0.0007850634
Marked as misclassified No
Message-id <4C1F4F84.9020608@egenix.com>
In-reply-to <1277118759.79.0.0329749809003.issue8854@psf.upfronthosting.co.za>
Content
Konstantin Zemlyak wrote:
> 
> Konstantin Zemlyak <zart@zartsoft.ru> added the comment:
> 
> Win2003 x64, VS2008, vanilla python 2.7rc1 amd64 from python.org.
> Building python packages with C extensions works fine. Tested on simplejson, jinja2 (with enabled speedups) and PIL.

I assume that you built without the patch applied. Does it also work
with the patch ?

This is the relevant section from the KB article:

"""
When you install a new program or when you run a program on a Windows x64 Edition computer, registry
calls made by 64-bit programs access the HKEY_LOCAL_MACHINE\Software registry sub key without
redirection. WOW64 intercepts registry calls to HKEY_LOCAL_MACHINE\Software that are made by 32-bit
programs, and then redirects them to the HKEY_LOCAL_MACHINE\Software\WOW6432node sub key.
"""

Since VS2008 is a 32-bit application, the registry keys are written
to the HKEY_LOCAL_MACHINE\Software\WOW6432node branch.

64-bit applications such as Python AMD64 don't see this indirection,
so they have to explicitly look in that branch to find VS2008 settings.

I checked the registry on the machine and indeed the VS2008 keys are
only available under the HKEY_LOCAL_MACHINE\Software\WOW6432node branch.
History
Date User Action Args
2010-06-21 11:39:52lemburgsetrecipients: + lemburg, loewis, benjamin.peterson, tarek, srid, zart
2010-06-21 11:39:51lemburglinkissue8854 messages
2010-06-21 11:39:50lemburgcreate