[Python-Dev] PEP 384 status
fuzzyman at voidspace.org.uk
Wed Sep 1 15:04:12 CEST 2010
On 01/09/2010 13:54, Antoine Pitrou wrote:
> Please consider this: even without relying on PEP 384, using FILE*
> is /already/ dangerous; because you might compile an extension with a
> different compiler version than Python was compiled with. So, if we were
> following you, we should rip out PyObject_Print() of the whole C API,
> not only the limited subset which is defined by PEP 384.
Definitely. On Windows it is relatively common to configure distutils to
compile extensions with Mingw, which is likely to have problems with
FILE* from the Microsoft C runtime .
 I say *likely* because I have vague memories of Mingw being able to
compile against msvcrt, but I'm not sure about this. This is actually
less of an issue at the moment as we are now using a Microsoft compiler
for which a free version is available. This wasn't the case for a while
(and still isn't for those using Python 2.5 and earlier).
> (now I have nothing against completely ripping out PyObject_Print() if
> we find out that it's not really useful...)
> Python-Dev mailing list
> Python-Dev at python.org
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
More information about the Python-Dev