This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients eric.araujo, jonny, loewis, rpetrov
Date 2010-12-04.20:06:52
SpamBayes Score 7.8723694e-11
Marked as misclassified No
Message-id <4CFA9F5B.8090808@v.loewis.de>
In-reply-to <1291493040.53.0.877788804226.issue10615@psf.upfronthosting.co.za>
Content
> After all, the Win32 platform is not that uncommon. I know, MinGW
> could be seen as a different platform, but I never encountered a
> situation where I required anything but the exe file (no special
> MinGW DLL or something like that).

Traditionally, MingW-compiled Python binaries would often be
binary-incompatible with the ones available from python.org, since the
MingW build would use a different version of the MS CRT than the
python.org version. As a consequence, extensions built for the official
binaries would crash in the MingW build, and vice versa.
History
Date User Action Args
2010-12-04 20:06:53loewissetrecipients: + loewis, eric.araujo, rpetrov, jonny
2010-12-04 20:06:52loewislinkissue10615 messages
2010-12-04 20:06:52loewiscreate