➜

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, tarek
Date 2010-06-21.08:43:02
SpamBayes Score 5.46528e-05
Marked as misclassified No
Message-id <4C1F2615.8020907@egenix.com>
In-reply-to <1277070057.74.0.976372191789.issue8854@psf.upfronthosting.co.za>
Content 
Tarek Ziadé wrote:
> 
> Tarek Ziadé <ziade.tarek@gmail.com> added the comment:
> 
> The patch looks good but I am not comfortable with this change until it's tested under other windows/VC flavors.

The patch is really trivial, but I'll test it on a Windows x86
installation as well today.

Would be great if we could get someone else test it on their
Windows x64 system.

It's strange that noone has noticed this problem while Python 2.6
was out. I know that Martin uses a cross-compiling setup to create
the 64-bit installers, so he wouldn't have noticed, but others
should have seen similar problems, trying to compile extensions
on Windows x64.

I guess most people still use the 32-bit Python installers on Windows
x64 systems.
History
Date User Action Args
2010-06-21 08:43:05lemburgsetrecipients: + lemburg, loewis, benjamin.peterson, tarek
2010-06-21 08:43:03lemburglinkissue8854 messages
2010-06-21 08:43:02lemburgcreate