wxPython is now creating it's own manifest dynamically at runtime, and the ones attached to the binaries are whatever is done by default by the compiler and/or distutils.
···
On 12/20/10 1:22 AM, BartonC wrote:
I've checked both ANSI and UNICODE versions of the 2.8.11.0 binaries for
python 2.6 and 2.7
In the 2.6 build we see:
...
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC90.CRT"
version="9.0.21022.8" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
...In the 2.7 build we see
...
<dependency></dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls"
version="6.0.0.0" processorArchitecture="x86"
publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity>
</dependentAssembly>
</dependency>
...This may be the cause of much grief when the pythonXX.dll is loaded from
managed code (PythonDotNet (which I am actively developing/testing
against 2.7 for release.)
--
Robin Dunn
Software Craftsman