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 Matt.Hickford
Recipients Matt.Hickford, dstufft, eric.araujo, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-09-29.15:58:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAGJzqs=jyP_-V2ZTnOMSSL2zCo8+EQ2_4ioV7d8TTyzOFtpn4g@mail.gmail.com>
In-reply-to <1443540261.1.0.644462443691.issue25250@psf.upfronthosting.co.za>
Content
Yes you're right. My setup.py if you're curious
https://github.com/hickford/primesieve-python/blob/master/setup.py

Separately, I think compiler=mingw32 is broken in Python 3.5 on computers
with Visual Studio 2015 installed.  http://bugs.python.org/issue25251 if
that interests you

On 29 September 2015 at 16:24, Steve Dower <report@bugs.python.org> wrote:

>
> Steve Dower added the comment:
>
> 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.
>
> ----------
> resolution:  -> not a bug
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue25250>
> _______________________________________
>
History
Date User Action Args
2015-09-29 15:58:21Matt.Hickfordsetrecipients: + Matt.Hickford, paul.moore, tim.golden, eric.araujo, zach.ware, steve.dower, dstufft
2015-09-29 15:58:21Matt.Hickfordlinkissue25250 messages
2015-09-29 15:58:21Matt.Hickfordcreate