Logged In: YES 
user_id=299547

I think we misunderstand each other. My intention was not to
force anyone to change his compiler.

AFAIK there is no AMD64 support prior to VS2005 (i.e.
compiler version 14.00). Therefore as soon as one has to
compile for AMD64 he runs into the initial problem of this
bug report.

The only thing I am asking for is to incorporate a
(hopefully small) VS2005 specific workaround in the source
code of Python.

The default compiler should remain VS2003 (i.e. compiler
version 13.10). So no one has to change his compiler.
However people that are forced to use VS2005 do not run into
this specific problem anymore.