Martin v. Löwis wrote: >>> At first glance, this is a minor issue - passing FILE* pointers >>> across >>> DLL boundaries isn't something I'd normally expect people to do - >>> but >>> look further and you find you're opening a real can of worms. For >>> example, Python has public APIs which take FILE* parameters. >> >> >> So convert them to taking PyWrappedFile * parameters. > > Easy to say, hard to do.
But *that's* the solution for this problem. It's always been like this under Windows and will always be. Changing back to msvcrt so that people must compile their extension with non-standard compilation options it's really *worse* than just requiring msvcrt71 and punt. There's also a free compiler from Microsoft and tons of webpages which say how to compile with it. Or with mingw, even. So, I really believe that the situation is settling down. People are doing what they want to, with some difficulties perhaps, but there's nothing really undoable. If another change has to be pursued, it is to abstract Python from CRT altogether, or at least across boundaries. -- Giovanni Bajo _______________________________________________ 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
