Le lundi 30 août 2010 à 22:18 +1000, Nick Coghlan a écrit : > > FILE* is very different from the other things you mention. Function > call conventions and binary representations are defined in the C > standard. FILE*, on the other hand, is explicitly called out as an > opaque reference completely under the control of the specific C > runtime implementation. > > Since the Linkage section of PEP 384 specifically states the > availability of a generic "python3.dll" that dynamically redirects to > the relevant "python3y.dll" to allow an extension module to run > against any 3.2 or later Python version as a goal of the PEP, I would > say that allowing mixing of C runtimes is definitely one of the PEP's > goals.
Well, allowing it is one thing. Guaranteeing that it will always work is another one. That said, I have nothing against Python providing such a guarantee, as long as it doesn't complicate the work of developers on other platforms who don't care about Windows. Regards Antoine. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
