On Wed, Oct 29, 2014 at 3:25 PM, Antoine Pitrou <solipsis@pitrou.net> wrote:
On Thu, 30 Oct 2014 01:09:45 +1000
Nick Coghlan <ncoghlan@gmail.com> wrote:
>
> Lots of folks are happy with POSIX emulation layers on Windows, as
> they're OK with "basically works" rather than "works like any other
> native application". "Basically works" isn't sufficient for many
> Python-on-Windows use cases though, so the core ABI is a platform
> native one, rather than a POSIX emulation.
>
> This makes Python fit in more cleanly with other Windows applications,
> but makes it harder to write Python applications that span both POSIX
> and Windows.

I don't really understanding why that's the case. Only the
building and packaging may be more difficult, and that assumes you're
familiar with mingw32. But mingw32, AFAIK, doesn't make the Windows
runtime magically POSIX-compatible (Cygwin does, to some extent).

mingw32 is a more compliant C compiler (VS2008 does not implement much from C89), and it does implement quite a few things not implemented in the C runtime, especially for math.

But TBH, those are not compelling cases to build python itself on mingw, only to better support C extensions with mingw.

David


Regards

Antoine.