[issue13892] distutils handling of windows manifest isn't optimal

Change by Irit Katriel : -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bu

[issue13892] distutils handling of windows manifest isn't optimal

Jack Jansen added the comment: Indeed, my situation is different from the cscript.exe situation because in my case Python needs to call back into the hosting application. Further experiments have shown that this is indeed the problem, and moreover that this is a problem that cannot be solved

[issue13892] distutils handling of windows manifest isn't optimal

Jack Jansen added the comment: Hmm, the cscript.exe point is a valid one. I can think of two things that make my situation different, I will investigate (and post here): - I started getting the problem when the hosting application (Ambulant multimedia player) switched from VS2008 to VS2010. S

[issue13892] distutils handling of windows manifest isn't optimal

Mark Hammond added the comment: I thought this shouldn't be a problem - that as pythonxx.dll contains a manifest with the references and also contains hoops to ensure its "activation context" is used when loading dynamic modules, that things should work correctly. The scenario you outline is

[issue13892] distutils handling of windows manifest isn't optimal

Changes by Éric Araujo : -- nosy: +mhammond ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue13892] distutils handling of windows manifest isn't optimal

New submission from Jack Jansen : I found a problem with the handling of manifest files in the msvc9compiler. Distutils removes the reference to the MSVC runtime from the manifest resource, to enable installing the runtime system locally (i.e. to allow non-admins to install Python in their own