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

[Luke Kenneth Casson Leighton]

On Thu, Jan 22, 2009 at 8:17 PM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>>  am i right?
>
> You should test that. I'm not sure whether it will crash (in particular,
> it might not on load), but it *might* crash, or fail in strange ways
> (e.g. when it checks whether something is a string, and decides it is
> not, because it is looking at the other PyString_Type)

 mrmmm... how? apps won't end up loading _both_ libpython2.5.dll _and_
python25.dll (or libpython2.N.dll and python2N.dll) will they?

>> and if _that's_ the case, i can stop fricking about with msvcr80  :)
>
> If so, I think there is little point in submitting patches to the Python
> bug tracker. I'm -1 on supporting two different-but-similar builds on
> Windows. I could accept a different build *process*, but the outcome
> must be the same either way.
>
> (of course, msvcr80 is irrelevant, because Python had never been using
> that officially)

 oh?  i saw the PCbuild8 and thought it was.  oh that's even better -
if python2.5 only officially support msvcrt whew.

ok , i see - python2.6 uses msvcr90.

 i'll cross that bridge when i come to it.

l.

> Regards,
> Martin
>