Message258395
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. |
|
Date |
User |
Action |
Args |
2016-01-16 16:20:10 | eryksun | set | recipients:
+ eryksun, loewis, paul.moore, tim.golden, benjamin.peterson, zach.ware, steve.dower, David Rader |
2016-01-16 16:20:10 | eryksun | set | messageid: <1452961210.09.0.182956699557.issue26132@psf.upfronthosting.co.za> |
2016-01-16 16:20:10 | eryksun | link | issue26132 messages |
2016-01-16 16:20:09 | eryksun | create | |
|