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.
</F> On Fri, Oct 2, 2009 at 12:10 AM, Farshid Lashkari <fla...@gmail.com> wrote: > 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 bug report. The change > was only made to the PCbuild/pyd.vsprops file, which I don't believe will > affect 3rd party extensions. I see that Koen submitted a patch > for msvc9compiler.py that will strip the runtime from the manifest, but that > doesn't appear to have been committed. So I'm not really sure how 3rd party > extension developers can build pyd files without embedded manifests. > On Thu, Oct 1, 2009 at 4:10 AM, Fredrik Lundh <fred...@pythonware.com> > wrote: >> >> 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. >> >> </F> >> >> On Mon, Sep 28, 2009 at 4:07 PM, Fredrik Lundh <fred...@pythonware.com> >> wrote: >> > 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! >> > >> > </F> >> > >> > On Mon, Sep 28, 2009 at 3:46 PM, Koen van de Sande >> > <koenvandesa...@gmail.com> wrote: >> >> 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 setup.py build_ext call, so no changes to PIL >> >> should be >> >> needed. >> >> >> >> Koen >> >> _______________________________________________ >> >> Image-SIG maillist - image-...@python.org >> >> http://mail.python.org/mailman/listinfo/image-sig >> >> >> > >> _______________________________________________ >> Image-SIG maillist - image-...@python.org >> http://mail.python.org/mailman/listinfo/image-sig > > _______________________________________________ Image-SIG maillist - Image-SIG@python.org http://mail.python.org/mailman/listinfo/image-sig
