Author steve.dower
Recipients cgohlke, eryksun, larry, paul.moore, skrah, steve.dower, tim.golden, zach.ware
Date 2015-09-09.02:29:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441765743.95.0.12325157659.issue25027@psf.upfronthosting.co.za>
In-reply-to
Content
Okay, here's a proposal:

We bundle vcruntime140.dll with Python's normal install, so it's always there and extensions that use it do not need to ship anything.

When distutils._msvccompiler is used to build an extension with a *different* version of MSVC, it will copy the dependency or statically link (as in my attached patch).

This does not prevent us from changing the compiler used for 3.5, as long as we continue to ship both vcruntime140.dll and the newer version, and extensions build with newer compilers will include the dependency or pick up the bundled one if they are on a version that includes it.

(Extensions that use C++ and depend on msvcp###.dll will need to ship that themselves, obviously.)

I'll post a new patch shortly, but it's only a very small change from this one for distutils, and the rest is in the installer.
History
Date User Action Args
2015-09-09 02:29:04steve.dowersetrecipients: + steve.dower, paul.moore, larry, tim.golden, cgohlke, skrah, zach.ware, eryksun
2015-09-09 02:29:03steve.dowersetmessageid: <1441765743.95.0.12325157659.issue25027@psf.upfronthosting.co.za>
2015-09-09 02:29:03steve.dowerlinkissue25027 messages
2015-09-09 02:29:03steve.dowercreate