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

Roumen Petrov bugtrack at roumenpetrov.info
Fri Jan 23 23:48:48 CET 2009

Luke Kenneth Casson Leighton wrote:
>> python.exe (say, the official one) loads
>> python25.dll. Then, an import is made of a ming-wine extension, say
>> foo.pyd, which is linked with libpython2.5.dll, which then gets loaded.
>> Voila, you have two interpreters in memory, with different type objects,
>> memory heaps, and so on.
>  ok, there's a solution for that - the gist of the solution is already
> implemented in things like Apache Runtime and Apache2 (modules), and
> is an extremely common standard technique implemented in OS kernels.
> the "old school" name for it is "vector tables".
[SNIP] Did you think that this will escape python MSVC from "Assembly 
hell" ?


More information about the Python-Dev mailing list