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 steve.dower
Recipients carlkl, erik flister, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2015-06-15.21:04:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> python-3.5b2 is linked against the newly introduced 'universal CRT', that is without any doubt a SYSTEM LIBRARY. However, heap memory managment functions and other functions are linked against VCRUNTIME140.dll instead of the ucrtbase.dll. Is this the intended behavior? 

AFAICT, all of the "public" functions exported from vcruntime140.dll are also exported from api-ms-win-crt-string-l1-1-0.dll (which forwards to ucrtbase.dll), which would make them available as part of the stable ABI. I'm not sure why vcruntime140.dll has its own versions or why they are used in preference, but it may be to do with inlining or intrinsics.

vcruntime140.dll exists and is not guaranteed stable because it provides functionality that needs intimate knowledge of the compiler (stack unwinding, etc.). Those string APIs don't make much sense here, so I'd guess they're dependencies that had to be pulled in, and the linker may just be prioritizing those ones by accident.

I would not be at all surprised if MinGW had to replace vcruntime140.dll entirely. Nothing from ucrtbase.dll can depend on it, so replacing it is probably for the best. Then just link against either the ucrtbase.dll or the api-ms-win-crt-*.dll libraries.
Date User Action Args
2015-06-15 21:04:03steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun, carlkl, erik flister
2015-06-15 21:04:03steve.dowersetmessageid: <>
2015-06-15 21:04:03steve.dowerlinkissue24429 messages
2015-06-15 21:04:03steve.dowercreate