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 Matt.Hickford, dstufft, eric.araujo, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-09-29.15:24:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443540261.1.0.644462443691.issue25250@psf.upfronthosting.co.za>
In-reply-to
Content
Once you've established that MSVC is being used, you can infer the version from the Python version, is what I meant by "it doesn't matter". The version attribute on the compiler instance is never going to differ pre-3.5, and post-3.5 it doesn't even exist.

Generally, I'd say you're safer to detect and check _MSC_VER in your C code if it's relevant, as that will also handle builds that don't go via your setup.py.
History
Date User Action Args
2015-09-29 15:24:21steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, eric.araujo, Matt.Hickford, zach.ware, dstufft
2015-09-29 15:24:21steve.dowersetmessageid: <1443540261.1.0.644462443691.issue25250@psf.upfronthosting.co.za>
2015-09-29 15:24:21steve.dowerlinkissue25250 messages
2015-09-29 15:24:21steve.dowercreate