[issue31340] Use VS 2017 compiler for build

Christoph Gohlke added the comment: > Have you confirmed that's a problem? No, I have not noticed any problems yet with with Python 3.7.0a3 and many extensions built with VS2017.5. -- ___ Python tracker ___

[issue31340] Use VS 2017 compiler for build

Steve Dower added the comment: Have you confirmed that's a problem? There are new compatibility promises that did not exist for earlier versions of the runtime, but that does not mean there are no bugs. -- ___ Python tracker

[issue31340] Use VS 2017 compiler for build

Christoph Gohlke added the comment: Since this has not been reverted/changed for 3.6.4 or 3.7.0a3, another potential issue arises: C extensions that are compiled with Visual Studio 2017 are linked to a newer version of vcruntime140.dll (latest is 14.12.25810, VS2017 15.5) than the DLL shipped

[issue31340] Use VS 2017 compiler for build

Steve Dower added the comment: No, but if we need to do 3.6.4 quickly for another reason, let me know and I'll make this change. It only affects people who are trying to share intermediate build files (which for MSVC purposes, includes static libraries) between their 3.6.2 and 3.6.3 builds.

[issue31340] Use VS 2017 compiler for build

Ned Deily added the comment: If you think we should do a 3.6.4 to address this, we can do that. I'll leave it up to your judgement. -- ___ Python tracker ___

[issue31340] Use VS 2017 compiler for build

Steve Dower added the comment: > How about giving priority to VS 2015 That would be the fix, but it's not worth releasing an immediate 3.6.4 IMHO and by the time 3.6.4 comes about it could be more pain to change back than to leave it. That's the balance I'm thinking about for a while. Includ

[issue31340] Use VS 2017 compiler for build

Christoph Gohlke added the comment: I build most of my binaries after calling the correct vcvarsall.bat so I did not notice until today, when I was trying to build outside that environment. Also, I misread your comment (https://bugs.python.org/issue31340#msg301538) earlier and did not worry

[issue31340] Use VS 2017 compiler for build

Steve Dower added the comment: Build artifacts (static libraries, in this case) are not compatible, but the built binaries are. This may be a reasonable argument for not updating distutils's support in minor versions (and I'm totally happy to just stop updating distutils period - see the rec

[issue31340] Use VS 2017 compiler for build

Christoph Gohlke added the comment: I have Visual Studio 2015 and Visual Studio 2017 Community editions with latest patches installed. Building a minimal C extension on Python 3.6.3 with distutils now uses MSVC 14.11.25503. That is unexpected. When building complex extensions that link to st

[issue31340] Use VS 2017 compiler for build

INADA Naoki added the comment: Nice! VS2017 is much lighter than VS2015 for install size! https://blogs.msdn.microsoft.com/vcblog/2016/08/22/the-lightweight-visual-studio-15-installer/ -- nosy: +inada.naoki ___ Python tracker

[issue31340] Use VS 2017 compiler for build

Steve Dower added the comment: Note that this should not change anything for 3.6, but enables using VS 2017 to build. If you only have VS 2015 then it will use that, and I've enabled AppVeyor for both to make sure we keep it that way. 3.7 will also build with either, but there isn't as much im

[issue31340] Use VS 2017 compiler for build

Steve Dower added the comment: New changeset fd645ec6f5696e841e6d49075f9fd81e54e74d91 by Steve Dower in branch '3.6': [3.6] bpo-31340: Change to building with MSVC v141 (included with Visual Studio 2017) (GH-3311) (#3386) https://github.com/python/cpython/commit/fd645ec6f5696e841e6d49075f9fd81

[issue31340] Use VS 2017 compiler for build

Changes by Steve Dower : -- stage: needs patch -> backport needed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue31340] Use VS 2017 compiler for build

Changes by Steve Dower : -- pull_requests: +3393 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue31340] Use VS 2017 compiler for build

Steve Dower added the comment: New changeset 5fcd5e64eec9ed67613b8fe7356fb8288151ceba by Steve Dower in branch 'master': bpo-31340: Change to building with MSVC v141 (included with Visual Studio 2017) (#3311) https://github.com/python/cpython/commit/5fcd5e64eec9ed67613b8fe7356fb8288151ceba -

[issue31340] Use VS 2017 compiler for build

Changes by Steve Dower : -- pull_requests: +3339 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue31340] Use VS 2017 compiler for build

Changes by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue31340] Use VS 2017 compiler for build

New submission from Steve Dower: The newer MSVC (v141) is available and reliable, and theoretically binary compatible with v140. This means we can update both Python 3.6 and 3.7 to build with it. Testing for this should include: * pythoncore with v141 and remainder with v140 * Python with v141