Re: [Image-SIG] Windows CRT issues with Python 2.6

To check for the manifest, I just open it up in a hex editor and look for the word "manifest". That will get you to the XML part of the file, and you can see what's happening. Please note that if you turn manifests off, you assume that your extension has no other dependencies. And for things lik

Re: [Image-SIG] Windows CRT issues with Python 2.6

I use Resource Hacker (http://www.angusj.com/resourcehacker/), it allows you to view and edit all embedded resources of EXE/DLL files. It's a very handy application. Dependency Walker is really nice too. Regarding the issue, wouldn't it just be better to compile the pyd without any embedded manifes

Re: [Image-SIG] Windows CRT issues with Python 2.6

Hi, you can use Dependency Walker . If the patch is working, pyd files will depend on MSVCR90.DLL, otherwise %WINDIR%\winsxs\...\MSVCR90.DLL There are two issues with Koen's patch (both easy to fix). It does not work for 64-bit Python and it also processes e

Re: [Image-SIG] Windows CRT issues with Python 2.6

Open it in a hex editor, and look for the word manifest. This is what it looks like with dependency: uiAccess="false"> version="9.0.21022.8" processorArchitecture="x86" publicKeyToken="1fc8b3b9a1e18e3b"> PAPADDINGXXPADDINGPADDINGX and after th

Re: [Image-SIG] Windows CRT issues with Python 2.6

Ok, I can apply Koen's patch locally and rebuild, if that makes sense. What's the quickest way to look for embedded manifests in the PYD:s? dumpbin doesn't seem to say anything about that, so I assume I have to use some other tool. On Fri, Oct 2, 2009 at 12:10 AM, Farshid Lashkari wrote: > I j

Re: [Image-SIG] Windows CRT issues with Python 2.6

I just tried the new installer ( http://effbot.org/media/downloads/PIL-1.1.6.win32-py2.6.exe), but the pyd files still contain embedded manifests. The installer says it was built Oct 1, 2009 with Python 2.6.2, so that should be the latest version. I took a closer look at the changes made from that

Re: [Image-SIG] Windows CRT issues with Python 2.6

I've replaced the 1.1.6 binary at effbot.org/downloads with one built under 2.6.2. The installer is 130k larger thanks to a 3x larger wininst executable (!?), but the binary extensions are slightly smaller than before, so I'll assume it's the manifests that have disappeared. On Mon, Sep 28, 200

Re: [Image-SIG] Windows CRT issues with Python 2.6

Ah, sneaky. I'm pretty sure the current binary distribution was built when 2.6 was new, and I didn't really expect them to tweak build-related issues in an incremental release :) I'll push out a new build asap; will ping the list when it's available. Thanks! On Mon, Sep 28, 2009 at 3:46 PM, K

Re: [Image-SIG] Windows CRT issues with Python 2.6

The fix was applied to the main Python distribution (2.6.2 has it for sure, 2.6.0/2.6.1 does not). Any extension built with 2.6.2 or higher should be fine, as it will not get an embedded manifest. So just rebuild with Python Windows version 2.6.2. I see in the PIL source tree that it uses a setu

Re: [Image-SIG] Windows CRT issues with Python 2.6

Make sense, but I'm not sure I can figure out what they actually ended up doing about it from that thread. Anyone who can summarize and/or provide a patch? On Thu, Sep 10, 2009 at 8:00 PM, Farshid Lashkari wrote: > Hello, > I've encountered an issue with distributing a Python 2.6 and PIL based

[Image-SIG] Windows CRT issues with Python 2.6

Hello, I've encountered an issue with distributing a Python 2.6 and PIL based application on Windows computers that do not have the VC 9.0 CRT installed. The problem is that the _imaging.pyd module fails to load. I believe the reason is that the file has an embedded manifest specifying the CRT vers