h-vetinari <h.vetin...@gmx.com> added the comment:

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

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue42380>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to