[Python-Dev] PEP 384 status (original) (raw)

Nick Coghlan ncoghlan at gmail.com
Wed Sep 1 23:04:31 CEST 2010

On Wed, Sep 1, 2010 at 10:54 PM, Antoine Pitrou <solipsis at pitrou.net> 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 PyObjectPrint() of the whole C API, not only the limited subset which is defined by PEP 384.

(now I have nothing against completely ripping out PyObjectPrint() if we find out that it's not really useful...)

I think it would be better if everything dealing with FILE* was a macro rather than a function, yes. The definition of the limited API is a chance to fix that without incurring the cost in backwards incompatibility that would otherwise arise. Since we have that opportunity, why not take it?

Cheers, Nick.

-- Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list