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 loewis
Recipients Tom.Whittock, brian.curtin, loewis, r.david.murray
Date 2011-06-05.17:54:49
SpamBayes Score 2.1580349e-10
Marked as misclassified No
Message-id <1307296490.02.0.342566824772.issue12267@psf.upfronthosting.co.za>
In-reply-to
Content
I'm rejecting this patch - it's not the right approach to this problem.

If we want to support VS 2010 project files in some form, we should generate them out of the VS 2008 files, similar to the vs9to8 script. The conversion result should definitely support AMD64 builds - as Brian points out, VS 2010 *does* support AMD64, if the SDK is installed. 

Given that the automatic conversion works fairly well, though, I don't think anything needs to be done for 2.7 (except perhaps writing some documentation into PCbuild/readme.txt).

For 3.3, I would personally favor if Python would skip over VS 2010, and move right to VS 2012 (please don't discuss this aspect in this issue).
History
Date User Action Args
2011-06-05 17:54:50loewissetrecipients: + loewis, r.david.murray, brian.curtin, Tom.Whittock
2011-06-05 17:54:50loewissetmessageid: <1307296490.02.0.342566824772.issue12267@psf.upfronthosting.co.za>
2011-06-05 17:54:49loewislinkissue12267 messages
2011-06-05 17:54:49loewiscreate