Mark Hammond wrote: > > What happens if you give that executable a manifest referencing the CRT? > Note that things changed since pywin32 build 214 - now (almost) none > of the pywin32 pyd files have a manifest at all, meaning they can be > loaded correctly by Python itself in all cases - but the thing that > loads Python *must* have a manifest - ie, python.exe needs (and has) > one, as does the DLL which loads Python COM objects. It gets even more > complicated if Python is loaded via LoadLibrary - you can check the > source to pythoncomloader in the pywin32 repo for more details (the > short version is that the same hacks that Python itself does WRT > "activation contexts" needs to be done...)
Let us HOPE that Python quickly migrates to Visual Studio 2010, in which the team has wisely decided to abandon the side-by-side stuff altogether and go back to a simpler way of life, where having the files in \Windows\System32 is enough for everyone. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
