On Thu, Sep 8, 2011 at 11:24 PM, Mark Hammond <mhamm...@skippinet.com.au> wrote: > I guess you are saying that that module will have no reference to the CRT > assembly and that you will rebuild it so it does and that will fix the > problem?
I am rebuilding to ensure that the CRT reference is included in the DLL manifest for the extension. > > If so, that surprises me. To get as far as you did, much of the pywin32 > framework was imported, so all those modules must have imported OK. I don't know why the imported pyd files are not picking up the version from pythoncomloader26.dll, but I got the idea to stop removing msvcrt from the manifest from this stack overflow post: http://stackoverflow.com/questions/3706293/why-do-no-python-dlls-built-with-msvc-load-with-mod-wsgi and ended up at these python bugs as the source of the current state of things: http://bugs.python.org/issue4120 http://bugs.python.org/issue4566 Assuming that the fix from bug 4566 has been applied also to pythoncomloader26.dll perhaps there is some other kind of interaction on Windows 7 x64? I do have a Windows Vista x32 machine I could test on. Is it also possible that I am missing some dependency like the exact version of msvcr90.dll that is used with the pywin32 build? -Chris -- Christopher Lambacher ch...@kateandchris.net _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
