[issue6919] Link CRT Statically

Henri Hein added the comment: Right, I was thinking about rebuilding Python26.dll. If we do go down that path, I will report the results. Thanks for the feedback. -- ___ Python tracker __

[issue6919] Link CRT Statically

Martin v. Löwis added the comment: > If you do not *want* to change it, that is your prerogative, but it > *can* definitely work. I don't believe it can work; Amaury has already given a number of reasons. If you still believe otherwise, and want to see something change, please try coming up wi

[issue6919] Link CRT Statically

Amaury Forgeot d'Arc added the comment: It will seem to work for simple scripts, but many extension modules won't behave properly because: - some API functions (PyFile_AsFile, many PyRun_*functions, PyMarshal_*+FromFile) pass FILE* structures, which differ between instances of the CRT. - file de

[issue6919] Link CRT Statically

Henri Hein added the comment: If you do not *want* to change it, that is your prerogative, but it *can* definitely work. -- ___ Python tracker ___ __

[issue6919] Link CRT Statically

Changes by Georg Brandl : -- resolution: -> rejected status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue6919] Link CRT Statically

Martin v. Löwis added the comment: This can't possibly work. Extension modules that also link with the CRT will thus end with a separate copy of the CRT global state, causing crashes. -- nosy: +loewis ___ Python tracker

[issue6919] Link CRT Statically

New submission from Henri Hein : Suggestion: Link the CRT statically into Python26.dll/PythonNN.dll and compiled .PYD files, at least when using the Microsoft compiler. There has been a number of bugs related to the msvcrt.dll, msvcr90.dll, etc. Many of these would go away if the CRT was