Eryk Sun added the comment:
Steve, is this something that can only be reproduced on Windows 7/2008 for some
reason? My "just for me" installation on Windows 10 seems to work fine. I
installed from "python-2.7.11.amd64.msi" with the MD5 sum
25acca42662d4b02682eee0df3f3446d, which matches the MD5 sum posted on
python.org.
The resource #1 manifest embedded in python.exe uses the following assembly:
<assemblyIdentity type="win32"
name="Microsoft.VC90.CRT"
version="9.0.21022.8"
processorArchitecture="amd64"
publicKeyToken="1fc8b3b9a1e18e3b">
</assemblyIdentity>
The resource #2 manifest embedded in python27.dll uses the same assembly.
However, I can confirm the second problem. The extension modules in DLLs
incorrectly have a resource #2 manifest. They should be relying on the
activation context from the #2 manifest in python27.dll.
----------
nosy: +eryksun
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26132>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
