Matt Hickford added the comment: 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 <rep...@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 <rep...@bugs.python.org> > <http://bugs.python.org/issue25250> > _______________________________________ > ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25250> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
