On 21 November 2013 22:51, Christian Heimes <christ...@python.org> wrote: > Am 21.11.2013 12:31, schrieb mar...@v.loewis.de: >> That sounds doable. If we provided a "python2.dll", would could make the >> header files using the "restricted API" by default if Python is compiled >> with VS 2010. Extension builders could then regularly compile their >> extensions with VS 2010, or VS 2013, despite Python itself being linked >> with the VS 2008 CRT. > > What about the CAPI functions like PyFile_FromFile() and PyFile_AsFile() > that take a FILE* as argument? Or functions like PyErr_SetFromErrno() > that use the errno thread local variable? These function will either > crash or not work properly with mixed CRTs. Every CRT has its own errno > TLS, so Python won't see the errno of a CRT100 function like open(2), > see http://bugs.python.org/issue15883 . > > I don't understand how a stable Python ABI solves the issue of unstable > CRT ABIs. Are you planning to address these issues?
The stable ABI excludes all the CRT dependent APIs - that is exactly the subset of the stable ABI restrictions that I am suggesting we should backport to 2.7.7 rather than Stackless making a 2.8 release just to update to a backwards incompatible C runtime on Windows. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
