Chris AtLee schrieb:
>> I would guess it is more an issue of 32bit + 64bit dynamic linking
>> having issues, but I could certainly be wrong.
>
> I don't think so, this was the 64bit version of Python 2.5. When I
> recompiled with the 2003 compiler it worked fine.
Again, what 2003 compiler did yo
Chris AtLee schrieb:
> I just got bitten by the runtime library incompatibility problem on
> windows when I tried to load a C extension compiled with MSVC 2005
> (64-bit) into Python 2.5.
>
> I realize that Python2.5 will continue to use MSVC 2003 for
> compatibility reasons, but I was curious if
On 2/28/07, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> "Chris AtLee" <[EMAIL PROTECTED]> wrote:
> > I just got bitten by the runtime library incompatibility problem on
> > windows when I tried to load a C extension compiled with MSVC 2005
> > (64-bit) into Python 2.5.
>
> I would guess it is more
"Chris AtLee" <[EMAIL PROTECTED]> wrote:
> I just got bitten by the runtime library incompatibility problem on
> windows when I tried to load a C extension compiled with MSVC 2005
> (64-bit) into Python 2.5.
I would guess it is more an issue of 32bit + 64bit dynamic linking
having issues, but I c
I just got bitten by the runtime library incompatibility problem on
windows when I tried to load a C extension compiled with MSVC 2005
(64-bit) into Python 2.5.
I realize that Python2.5 will continue to use MSVC 2003 for
compatibility reasons, but I was curious if any thought had been given
to the
