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 steve.dower
Recipients Maxime Belanger, christian.heimes, larry, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-12-12.15:29:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If you can't compile, security fixes aren't worth anything. And while we don't support XP, the v140_xp toolset is in more of a grey area. There are real ways you could be forced into using it besides targeting XP.

Max - I'd rather just remove the ifdef checks completely. Fairly sure I added them in the migration from VC10, but they are simply incorrect (the header is from the WinSDK which is not the same as _MSC_VER) and will always be there for the versions of the SDK we allow, even back to 3.5.
Date User Action Args
2017-12-12 15:29:40steve.dowersetrecipients: + steve.dower, paul.moore, larry, christian.heimes, tim.golden, zach.ware, Maxime Belanger
2017-12-12 15:29:40steve.dowersetmessageid: <>
2017-12-12 15:29:40steve.dowerlinkissue32282 messages
2017-12-12 15:29:40steve.dowercreate