A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2009-January/085354.html below:

[Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now

[Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for nowLuke Kenneth Casson Leighton lkcl at lkcl.net
Fri Jan 23 09:27:16 CET 2009
On Fri, Jan 23, 2009 at 8:08 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>  ironically, i started out with the intent of going for python2N.dll
>> interoperability.  then i noticed that all the other mingw ports
>> dropped the total-inclusion-of-all-modules .... because you _can_.
>
> What modules are built in and what modules are external doesn't affect
> interoperability wrt. (third-party) extension modules.

 ahhh .... sooo.... [said in a japanese kind of way that indicates
understanding...]
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4