➜

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 cgohlke
Recipients cgohlke, jkloth, methane, ned.deily, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-01-03.07:32:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514964731.37.0.467229070634.issue31340@psf.upfronthosting.co.za>
In-reply-to
Content 
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 with the CPython 3.6.4/3.7.0a3 installer (14.0.24210, VS2015 Update 3). There is no standard way C extensions that are compiled with VS2017 can load the correct/newer vcruntime140.dll. That said, I have not noticed any problems yet while testing with Python 3.7.0a3.
History
Date User Action Args
2018-01-03 07:32:11cgohlkesetrecipients: + cgohlke, paul.moore, tim.golden, jkloth, ned.deily, methane, zach.ware, steve.dower
2018-01-03 07:32:11cgohlkesetmessageid: <1514964731.37.0.467229070634.issue31340@psf.upfronthosting.co.za>
2018-01-03 07:32:11cgohlkelinkissue31340 messages
2018-01-03 07:32:10cgohlkecreate