Comment 2 for bug 333626

Comment 1 by varmaa, Mar 24, 2008

IIRC, the potential problem with this approach is that it means that two separate
instances of the C runtime exist in the same process space. This means that certain
things, like file pointers, can't be exchanged from one CRT instance to another--or
rather, they *can* be exchanged, but it'll cause a segfault. I believe that we
encountered this fairly early on in Enso development, but I'm not 100% sure. I was
also under the impression that the reason C extension modules like pywin32 require
you to download a different installer depending on your version of Python was due to
this issue.

Are there any major Python C extension modules that statically include the CRT like this?