[Python-Dev] Linking with mscvrt (original) (raw)
Neil Hodgson nyamatongwe at gmail.com
Thu Feb 9 08:29:39 CET 2006
- Previous message: [Python-Dev] email 3.1 for Python 2.5 using PEP 8 module names
- Next message: [Python-Dev] Linking with mscvrt
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Martin v. Löwis:
I don't think this would be good enough. I then also need a way to provide extension authors with an API that looks like the CRT, but isn't: they cannot realistically change all their code to use the wrapped objects. In a recent case, somebody tried to passed a FILE* to a postrgres DLL linked with a different CRT; he shouldn't need to change the entire postgres code to use the modified API.
The postgres example is strange to me as I'd never consider passing a FILE* over a DLL boundary. Maybe this is a Unix/Windows cultural thing due to such practices being more dangerous on Windows.
Also, there is still the redistribution issue: to redistribute msvcr71.dll, you need to own a MSVC license. People that want to use py2exe (or some such) are in trouble: they need to distribute both python25.dll, and msvcr71.dll. They are allowed to distribute the former, but (formally) not allowed to distribute the latter.
Link statically.
Neil
- Previous message: [Python-Dev] email 3.1 for Python 2.5 using PEP 8 module names
- Next message: [Python-Dev] Linking with mscvrt
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]