From doko at ubuntu.com Fri Feb 8 04:06:00 2013 From: doko at ubuntu.com (Matthias Klose) Date: Fri, 08 Feb 2013 04:06:00 +0100 Subject: [Image-SIG] pillow incompatibilities Message-ID: <51146B98.6010706@ubuntu.com> python-imaging packages for both Python2 and Python3 are now available in Ubuntu raring (which will become 13.04), and are expected in Debian experimental soon. See - https://launchpad.net/ubuntu/+source/python-imaging - http://packages.qa.debian.org/p/python-imaging.html Now, every package using python-imaging either fails to build, or fails to run, because Pillow was converted to an egg. Maybe not a bad idea, however it does break ~100 packages. So the idea which Barry and I came up with, was to ship a PILcompat.pth, and a directory with the "old" toplevel PIL modules, just importing from PIL, e.g. PILcompat/Image.py: from PIL import Image at least for all modules mentioned in the module reference (you can't add PIL directly to the .pth file, because relative imports break). From my point of view this should be shipped and installed by default in Pillow, when built for Python2. I think it's not necessary to do that for Python3, as the old PIL doesn't support Python3 anyway. For the details see https://launchpad.net/bugs/1112496 Matthias From aclark at aclark.net Fri Feb 8 13:21:02 2013 From: aclark at aclark.net (Alex Clark) Date: Fri, 8 Feb 2013 07:21:02 -0500 Subject: [Image-SIG] pillow incompatibilities References: <51146B98.6010706@ubuntu.com> Message-ID: On 2013-02-08 03:06:00 +0000, Matthias Klose said: > python-imaging packages for both Python2 and Python3 are now available > in Ubuntu > raring (which will become 13.04), and are expected in Debian > experimental soon. See > > - https://launchpad.net/ubuntu/+source/python-imaging > - http://packages.qa.debian.org/p/python-imaging.html > > Now, every package using python-imaging either fails to build, or fails to run, > because Pillow was converted to an egg. Maybe not a bad idea, however it does > break ~100 packages. I'm not sure if "Pillow was converted to an egg" is an accurate description of the problem. To me, converting to egg is synonomous with "from setuptools import setup" (vs. from distutils import setup) which is a change that happened in Pillow. But there were other changes like removing "PIL.pth" which I think is what is actually responsible for the inability to do: >>> import Image This was intentional. > So the idea which Barry and I came up with, was to ship a > PILcompat.pth, and a directory with the "old" toplevel PIL modules, just > importing from PIL, e.g. PILcompat/Image.py: > > from PIL import Image > > at least for all modules mentioned in the module reference (you can't add PIL > directly to the .pth file, because relative imports break). From my point of > view this should be shipped and installed by default in Pillow, when built for > Python2. I think it's not necessary to do that for Python3, as the old PIL > doesn't support Python3 anyway. That sounds like reverting one of the major changes facilitated by the fork, which I don't think is likely to happen. If you can do: >>> import Image you are using PIL, not Pillow. > > For the details see https://launchpad.net/bugs/1112496 Thanks for the update. Let me know if there is anything else I can do to help. > > Matthias > _______________________________________________ > Image-SIG maillist - Image-SIG at python.org > http://mail.python.org/mailman/listinfo/image-sig -- Alex Clark ? https://www.gittip.com/aclark4life/ From barry at python.org Fri Feb 8 16:33:50 2013 From: barry at python.org (Barry Warsaw) Date: Fri, 8 Feb 2013 10:33:50 -0500 Subject: [Image-SIG] pillow incompatibilities References: <51146B98.6010706@ubuntu.com> Message-ID: <20130208103350.289b7ffc@anarchist.wooz.org> On Feb 08, 2013, at 07:21 AM, Alex Clark wrote: >But there were other changes like removing "PIL.pth" >which I think is what is actually responsible for the inability to do: > >>> import Image > >This was intentional. And IMHO, a good thing. PIL/Pillow need not be so special as to make claim to so much of the top-level namespace. Of course, there's the backward compatibility problem to deal with, but this is the right long-term change. >That sounds like reverting one of the major changes facilitated by the fork, >which I don't think is likely to happen. If you can do: > >>>> import Image > >you are using PIL, not Pillow. I think that Matthias would like to just swap-in Pillow for PIL in Debian and Ubuntu. This gives application the additional opportunity to more easily port to Python 3. >> > For the details see https://launchpad.net/bugs/1112496 > >Thanks for the update. Let me know if there is anything else I can do to he >lp. One thing that would be helpful would be to review my merge proposal for that bug, to see if there are any other top-level modules that should be exposed by the PILcompat.pth file. The current set is described in Matthias's comment here: https://bugs.launchpad.net/ubuntu/+source/python-imaging/+bug/1112496/comments/13 with the merge proposal here: https://code.launchpad.net/~barry/ubuntu/raring/python-imaging/lp1112496/+merge/146740 Cheers, -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From neve at email.unc.edu Wed Feb 20 21:11:01 2013 From: neve at email.unc.edu (Ryan Neve) Date: Wed, 20 Feb 2013 15:11:01 -0500 Subject: [Image-SIG] Preserving EXIF data and image.info['dpi'] missing Message-ID: <51252DD5.4040703@email.unc.edu> I'm using PIL with a time lapse camera to add some text and a few reference lines to an image. I'm using jpeg, but may switch to ppm (converted from raw). I have two problems. First, it seems as if PIL can read EXIF data but not write it. Is this correct? I've seen a lot of posts asking this question, but no recent answers. I really need the EXIF data preserved when I save the image. Second, when saving, the default dpi is 72, not the original dpi. I saw someone suggest: image.save('file.jpeg', dpi = image.info['dpi']) but my image.info is {'exif':'very long string...'} with no dpi key. I ended up hard coding my (300,300) dpi, but this seems less than ideal. Thanks -- *Ryan Neve* University of North Carolina Institute of Marine Sciences 3431 Arendell St Morehead City, NC 28557 (252) 726-6841 x179 (252) 726.2426 Fax -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: neve.vcf Type: text/x-vcard Size: 300 bytes Desc: not available URL: From aclark at aclark.net Mon Feb 25 17:00:21 2013 From: aclark at aclark.net (Alex Clark) Date: Mon, 25 Feb 2013 11:00:21 -0500 Subject: [Image-SIG] PSF grant Message-ID: Dear Python Imaging Folks, I'm considering asking the PSF for a grant to fund my work on Pillow for Python 3, please add any comments/questions/concerns you may have here: - https://github.com/python-imaging/Pillow/issues/61 Thank you! Alex -- Alex Clark ? http://about.me/alex.clark From aclark at aclark.net Thu Feb 28 02:29:47 2013 From: aclark at aclark.net (Alex Clark) Date: Wed, 27 Feb 2013 20:29:47 -0500 Subject: [Image-SIG] PSF grant References: Message-ID: On 2013-02-25 16:00:21 +0000, Alex Clark said: > Dear Python Imaging Folks, > > > I'm considering asking the PSF for a grant to fund my work on Pillowfor > Python 3, please add any comments/questions/concerns you may havehere: > > > - https://github.com/python-imaging/Pillow/issues/61 > > > Thank you! Proposal I will send tomorrow, comments welcome: https://github.com/python-imaging/psf-grant-proposal > > > Alex -- Alex Clark ? http://about.me/alex.clark From tux.torvalds.wikipedia at gmail.com Sat Feb 2 21:39:49 2013 From: tux.torvalds.wikipedia at gmail.com (Tux Torvalds) Date: Sat, 02 Feb 2013 20:39:49 -0000 Subject: [Image-SIG] PIL Python3k Message-ID: <510D798B.5070706@gmail.com> Hey there! Will there ever be a python3 compatible version of PIL or is the project discontiued? Tux Torvalds From mr at ramendik.ru Tue Feb 5 13:07:19 2013 From: mr at ramendik.ru (Mikhail Ramendik) Date: Tue, 05 Feb 2013 12:07:19 -0000 Subject: [Image-SIG] Installer not working in Win7, Python 2.7 Message-ID: Hello, I want to install PIL on Windows 7. Python 2.7 is installed: == Python 2.7 (r27:82525, Jul 4 2010, 07:43:08) [MSC v.1500 64 bit (AMD64)] on win32 Type "copyright", "credits" or "license()" for more information. >>> == I have downloaded PIL-1.1.7.win32-py2.7.exe . But when I start it, I get a "Cannot install" message: "Python version 2.7 required, which was not found in the registry" Can I fix this somehow? -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -------------- next part -------------- An HTML attachment was scrubbed... URL: