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?
</F> On Thu, Sep 10, 2009 at 8:00 PM, Farshid Lashkari <fla...@gmail.com> wrote: > 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 version > to load, which causes it to ignore the CRT files in the Python exe folder. > The pyd files that ship with Python (_socket.pyd, etc..) do not have this > problem because they are built without an embedded manifest, which causes > them to inherit the CRT that is already loaded through the Python process. > You can find information about this at the following bug report > (http://bugs.python.org/issue4120). > Would it be possible to modify the PIL build process to not embed a manifest > for Windows pyd files? > Cheers, > Farshid > _______________________________________________ > 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
