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 brian.curtin
Recipients alexis, brian.curtin, eric.araujo, jackjansen, kristjan.jonsson, loewis, mark.dickinson, mhammond, sable, santoso.wijaya, sbt, tarek, tim.golden, vstinner
Date 2012-04-26.19:51:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1335469873.0.0.478541998345.issue13210@psf.upfronthosting.co.za>
In-reply-to
Content
VS11 opened the VS2010 project fine without doing conversion. Note that this just uses VS11 to work with the project in VS2010 mode with the 2010 compiler.

Doing the conversion to VS11's compiler is another thing to consider, although probably not until it goes RTM. I just ran the conversion from VS2010 to VS11 and it just sets "PlatformToolset" to "v110" in all vcxproj files. It didn't compile cleanly, having 25 projects succeed and 4 fail, but it was more than enough to get python_d.exe to run. A few tests failed, but they're the same as the failures on VS2010, so we're not far off from VS11 easily working.
History
Date User Action Args
2012-04-26 19:51:13brian.curtinsetrecipients: + brian.curtin, loewis, mhammond, jackjansen, mark.dickinson, kristjan.jonsson, vstinner, sable, tim.golden, tarek, eric.araujo, santoso.wijaya, alexis, sbt
2012-04-26 19:51:13brian.curtinsetmessageid: <1335469873.0.0.478541998345.issue13210@psf.upfronthosting.co.za>
2012-04-26 19:51:12brian.curtinlinkissue13210 messages
2012-04-26 19:51:12brian.curtincreate