This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author hankdane
Recipients hankdane, tarek
Date 2009-09-16.04:19:11
SpamBayes Score 2.9482186e-07
Marked as misclassified No
Message-id <1253074754.07.0.562289184303.issue6919@psf.upfronthosting.co.za>
In-reply-to
Content
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 
statically linked into PythonNN.dll.  

The advantages of dynamically linking the CRT are not clear.  The 
binaries are decreased a bit in size, but this is countered by having 
to redistribute the CRT DLL.  

Switching to static linking is a little more work than just flipping a 
switch, as you have to compensate for some of the initialization work 
the DLL does, but it is both doable and worth doing.
History
Date User Action Args
2009-09-16 04:19:14hankdanesetrecipients: + hankdane, tarek
2009-09-16 04:19:14hankdanesetmessageid: <1253074754.07.0.562289184303.issue6919@psf.upfronthosting.co.za>
2009-09-16 04:19:12hankdanelinkissue6919 messages
2009-09-16 04:19:11hankdanecreate