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 future of the 2.x series. Cheers, Chris
"Chris AtLee" <chris@atlee.ca> 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 could certainly be wrong.
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 future of the 2.x series.
IIUC, there exists a project file in PCBUILD8 for compiling with MSVC 2005. You should be able to recompile Python 2.5 with that compiler, though you may need to change some things (I've never tried myself). - Josiah
On 2/28/07, Josiah Carlson <jcarlson@uci.edu> wrote:
"Chris AtLee" <chris@atlee.ca> 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 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.
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 future of the 2.x series.
IIUC, there exists a project file in PCBUILD8 for compiling with MSVC 2005. You should be able to recompile Python 2.5 with that compiler, though you may need to change some things (I've never tried myself).
That is kind of a last-resort for me...I'd like for my code to work with all the other python extensions out there, which is why I switched to the 2003 compiler for now.
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 you recompile with? There is none. Regards, Martin
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 any thought had been given to the future of the 2.x series.
You are mistaken. The 64-bit versions (AMD64 and Itanium) are not compiled using MSVC 2003 - this product does not even include compilers for this platform. Instead, they are compiled with the SDK compilers. Regards, Martin
participants (3)
-
"Martin v. Löwis" -
Chris AtLee -
Josiah Carlson