http://permalink.gmane.org/gmane.comp.python.image hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.python.image/5366 <pre> Also, it's a pretty common practice for setup.py files to look in "standard" locations for includes -- i.e. marcports and fink locations on OS-X, maybe we should add the homebrew locations as well (though doesn't homebrew use use/local ? I'd think that would already be on the standard list. -Chris </pre> Chris Barker - NOAA Federal 2013-03-19T23:50:21 http://permalink.gmane.org/gmane.comp.python.image/5365 <pre> Not environment variable,s but there is a config file for that. There is some minimal documentation at: http://docs.python.org/2/install/index.html#distutils-configuration-files Mark S. _______________________________________________ Image-SIG maillist - Image-SIG&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/image-sig </pre> Mark Sienkiewicz 2013-03-18T14:28:10 http://permalink.gmane.org/gmane.comp.python.image/5364 <pre>On 2013-03-16 09:29:19 +0000, Felix Schwarz said: What are "special environment variables"? Variables you defined, or are you setting already existing vars… Yes, please submit it for review. I'm not sure I fully understand the issue yet, so maybe that will help. IIRC, brew uses very common lib and header path dirs (e.g. /usr/local/lib, /usr/local/include) and Pillow's setup.py certainly already checks those paths. It's good that you were able to get it to work by passing in the path, but I'm not sure why you had to. </pre> Alex Clark 2013-03-17T12:08:40 http://permalink.gmane.org/gmane.comp.python.image/5363 <pre>On 2013-03-16 13:23:20 +0000, Charlie Clark said: Thank you! The majority of that work was done by Brian Crowell (https://github.com/fluggo). </pre> Alex Clark 2013-03-16T23:30:17 http://permalink.gmane.org/gmane.comp.python.image/5362 <pre>Hi, Am 16.03.2013 13:15, schrieb Alex Clark: Very much so, yes. Can you check if you have the jpeg headers somehow installed system-wide? Is there anything in homebrew I can configure so the headers are linked also in the default include locations? fs _______________________________________________ Image-SIG maillist - Image-SIG&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/image-sig </pre> Felix Schwarz 2013-03-16T21:18:10 http://permalink.gmane.org/gmane.comp.python.image/5361 <pre>Am 15.03.2013, 18:44 Uhr, schrieb Alex Clark &lt;aclark&lt; at &gt;aclark.net&gt;: Congratulations on adding Python 3 support! Charlie </pre> Charlie Clark 2013-03-16T13:23:20 http://permalink.gmane.org/gmane.comp.python.image/5360 <pre> as a follow-up I hacked together a quick patch so that setup.py checks also special environment variables. Do you think that functionality is interesting for pillow? If so I can submit a pull request. fs _______________________________________________ Image-SIG maillist - Image-SIG&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/image-sig </pre> Felix Schwarz 2013-03-16T09:29:19 http://permalink.gmane.org/gmane.comp.python.image/5359 <pre>Hi Mark, Am 15.03.2013 22:24, schrieb Mark Sienkiewicz: That worked for me. Thanks a lot. Is there any way to set these parameters using environment variables? Pillow is being installed as a dependency for my library so it would be easier if users could set up something beforehand... Well, I have a virtualenv anyway so I don't need that. Thank you very much for your spot-on explanation. fs _______________________________________________ Image-SIG maillist - Image-SIG&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/image-sig </pre> Felix Schwarz 2013-03-16T09:10:15 http://permalink.gmane.org/gmane.comp.python.image/5358 <pre> Am 15.03.2013 22:13, schrieb Bruce Johnson: Maybe I'm missing something but as far as I know $PATH is only used to find executables but in my case I need to specify the include directory which is usually specified using '-I...' in the compiler call. fs _______________________________________________ Image-SIG maillist - Image-SIG&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/image-sig </pre> Felix Schwarz 2013-03-16T09:07:56 http://permalink.gmane.org/gmane.comp.python.image/5357 <pre>On 2013-03-15 20:44:23 +0000, Felix Schwarz said: You shouldn't have to. Could something else be wrong? I have the same OS and Homebrew libs… and I get this: -------------------------------------------------------------------- SETUP SUMMARY (Pillow 2.0.0 fork, originally based on PIL 1.1.7) -------------------------------------------------------------------- version 2.0.0 (Pillow) platform darwin 2.7.3 (default, Feb 11 2013, 07:30:37) [GCC 4.2.1 Compatible Apple LLVM 4.2 (clang-425.0.24)] -------------------------------------------------------------------- --- TKINTER support available --- JPEG support available --- ZLIB (PNG/ZIP) support available --- TIFF G3/G4 (experimental) support available --- FREETYPE2 support available --- LITTLECMS support available *** WEBP support not available -------------------------------------------------------------------- To add a missing option, make sure you have the required </pre> Alex Clark 2013-03-15T22:46:36 http://permalink.gmane.org/gmane.comp.python.image/5356 <pre> On Mar 15, 2013, at 1:44 PM, Felix Schwarz &lt;felix.schwarz&lt; at &gt;oss.schwarz.eu&gt; wrote: Make sure ~/homebrew/include is on your $PATH? </pre> Bruce Johnson 2013-03-15T21:13:52 http://permalink.gmane.org/gmane.comp.python.image/5355 <pre> There are parameters for setup.py to specify where the include files and library files are. The interface is a bit klunky, but it worked like this for me: build_ext means to build the C extensions; this command recognizes -I for another directory of include files and -L for another directory of library files python setup.py build_ext -I ~/homebrew/include -L ~/homebrew/lib build means to do both the python and the C extension, but distutils recognizes that the C extension is built already, so you don't need to specify -I/-L -- a good thing, because it doesn't recognize them! python setup.py build install copies the build files to the install directory; the above commands did all of the build steps python setup.py install There are options to specify a specific directory to install in. I usually use: python setup.py install --home ~/py to get ~/py/bin (add to PATH) and ~/py/lib/python (add to PYTHONPATH). Regards, Mark S. _______________________________________________ Image-SI</pre> Mark Sienkiewicz 2013-03-15T21:24:39 http://permalink.gmane.org/gmane.comp.python.image/5354 <pre>Hey, how can I specify the include dir for header files (jpeglib.h) for Pillow without modifying the source? I'm on OS X (Mountain Lion) and installed libjpeg using homebrew. There is a 'jpeglib.h' file in ~/homebrew/include but 'python setup.py build' still says 'no jpeg support'. Any ideas/pointers? fs _______________________________________________ Image-SIG maillist - Image-SIG&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/image-sig </pre> Felix Schwarz 2013-03-15T20:44:23 http://permalink.gmane.org/gmane.comp.python.image/5353 <pre>FYI, Pillow 2.0.0 released: - https://pypi.python.org/pypi/Pillow/2.0.0 Please report issues here: - https://github.com/python-imaging/Pillow/issues </pre> Alex Clark 2013-03-15T17:44:46 http://permalink.gmane.org/gmane.comp.python.image/5352 <pre>I don't know if anyone has ever set up an IRC channel for PIL, and I am assuming that no minds if I do (e.g. Fredrik). If you do mind, please let me know! Otherwise, please join me for PIL &amp; Pillow discussion on irc.freenode.net in the #pil channel. More details here: - http://python-imaging.github.com/Pillow/ Alex </pre> Alex Clark 2013-03-06T14:46:39 http://permalink.gmane.org/gmane.comp.python.image/5351 <pre>On 2013-02-28 01:29:47 +0000, Alex Clark said: Approved! Thank you PSF. Closed https://github.com/python-imaging/Pillow/issues/61. </pre> Alex Clark 2013-03-06T14:41:08 http://permalink.gmane.org/gmane.comp.python.image/5350 <pre>On 2013-02-25 16:00:21 +0000, Alex Clark said: Proposal I will send tomorrow, comments welcome: https://github.com/python-imaging/psf-grant-proposal </pre> Alex Clark 2013-02-28T01:29:47 http://permalink.gmane.org/gmane.comp.python.image/5349 <pre>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 </pre> Alex Clark 2013-02-25T16:00:21 http://permalink.gmane.org/gmane.comp.python.image/5348 <pre>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 </pre> Ryan Neve 2013-02-20T20:11:01 http://permalink.gmane.org/gmane.comp.python.image/5347 <pre> 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. 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. 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 _______________________________________________ Image-SIG maillist - Image-SIG&lt; at &gt;python.org http://mail.python.org/mailman/listinfo/image-sig </pre> Barry Warsaw 2013-02-08T15:33:50 http://permalink.gmane.org/gmane.comp.python.image/5346 <pre>On 2013-02-08 03:06:00 +0000, Matthias Klose said: 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: This was intentional. 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: you are using PIL, not Pillow. Thanks for the update. Let me know if there is anything else I can do to help. </pre> Alex Clark 2013-02-08T12:21:02 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.python.image