➜

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 h-vetinari
Recipients h-vetinari, paul.moore, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2021-01-29.10:15:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1611915306.16.0.438817075184.issue42380@roundup.psfhosted.org>
In-reply-to
Content 
Hey Terry

I had asked about this on discuss (https://discuss.python.org/t/toolchain-upgrade-on-windows/6377/2), and Steve provided some very valuable input.

In particular, building with the newer VS (that supports C11) should stay ABI-compatible with everything that has been built on Visual Studio 2015, 2017 and 2019:
> This is different from all previous Visual C++ versions, as they each had their own distinct runtime files, not shared with other versions.

(from https://docs.microsoft.com/en-gb/cpp/windows/universal-crt-deployment?view=msvc-160&viewFallbackFrom=vs-2019), due to the way the (now-)universal runtime is designed.

Thanks
History
Date User Action Args
2021-01-29 10:15:06h-vetinarisetrecipients: + h-vetinari, terry.reedy, paul.moore, tim.golden, zach.ware, steve.dower
2021-01-29 10:15:06h-vetinarisetmessageid: <1611915306.16.0.438817075184.issue42380@roundup.psfhosted.org>
2021-01-29 10:15:06h-vetinarilinkissue42380 messages
2021-01-29 10:15:05h-vetinaricreate