[Python-Dev] PEP 384 status

David Cournapeau cournape at gmail.com
Wed Sep 8 00:34:06 CEST 2010

On Wed, Sep 8, 2010 at 2:48 AM, M.-A. Lemburg <mal at egenix.com> wrote:
> "Martin v. Löwis" wrote:
>>> This sounds like the issues such a mix can cause are mostly
>>> theoretical and don't really bother much in practice, so
>>> PEP 384 on Windows does have a chance :-)
>> Actually, the CRT issues (FILE* in particular) have been
>> causing real crashes for many years, for many people.
> Do you have some pointers ?

I don't have a bug report, but I have had issues in my audiolab
package, where the package itself is built with visual studio, but the
library it is linked against is built with mingw (libsndfile, which
cannot be built with visual studio). The problem happens when you want
to use the mingw-built library which accepts a file descriptor that
you create with mkstemp inside code built with Visual Studio.

This issue is actually quite easy to reproduce.

> I don't remember this being a real practical issue, at least
> not for different versions of the MS CRTs.

I would turn the question around: what are the cases where you manage
to mix CRT and not getting any issues ? This has never worked in my
own experience in the context of python extensions,



More information about the Python-Dev mailing list