On 8/1/10 10:29 PM, in article 4c562da3.8030...@noaa.gov, Christopher
Barker chris.bar...@noaa.gov wrote:
Alex Clark wrote:
On 8/1/10 3:04 PM, in article 4c55c525.9090...@noaa.gov, Christopher
Barker chris.bar...@noaa.gov wrote:
Š
Is packaging the only issues this fork is for?
Yes.
2010/8/1 Jerome Leclanche adys...@gmail.com:
Although the PIL and Image* packages themselves do not
respect python standards (should be from imaging import .., or
something alike).
If you had been paying attention, you'd noticed that python
standards change all the time, depend on what the
2010/7/31 Daniel Fetchinson fetchin...@googlemail.com:
I have been wanting to tackle this for sometime, and finally got around to
it tonight. I've created a friendly fork of PIL called Pillow:
http://pypi.python.org/pypi/Pillow/1.0
Some background: I've been doing Plone development for the
On 8/1/10 6:51 AM, in article
aanlktik-mkenwtpsmfpcymd6enypb8un+qwqzj=ug...@mail.gmail.com, Fredrik
Lundh fred...@pythonware.com wrote:
2010/8/1 Jerome Leclanche adys...@gmail.com:
Although the PIL and Image* packages themselves do not
respect python standards (should be from imaging
On 8/1/10 7:04 AM, in article
aanlktikcnvggtjnwtiag0xnmkwdnu+qw2prnoetsv...@mail.gmail.com, Fredrik
Lundh fred...@pythonware.com wrote:
2010/7/31 Daniel Fetchinson fetchin...@googlemail.com:
I have been wanting to tackle this for sometime, and finally got around to
it tonight. I've created
Alex Clark wrote:
OK, I'm trying to figure this out. As I understand it, the result of the
incompatibility is that:
import Image
Fails in Zope 2 if PIL is installed because Zope 2 (OFS) has it's own Image
module.
For quite some time, PIL has been delivered as both a package and with a
pth
2010/8/1 Christopher Barker chris.bar...@noaa.gov:
I'd be a bit happier if import Image raised a deprecation warning, but I'm
not sure how you'd do that. (I actually did help do that for the GDAL
package, but that was set up differently - they actually had all their stuff
dumped directly into
On 8/1/10 3:04 PM, in article 4c55c525.9090...@noaa.gov, Christopher
Barker chris.bar...@noaa.gov wrote:
Is packaging the only issues this fork is for?
Yes. In Plone-land we rely a great deal on packages on PyPI. Buildout is a
tool (which my 'Plone site admin' book covers in great
Hi all,
I have been wanting to tackle this for sometime, and finally got around to
it tonight. I've created a friendly fork of PIL called Pillow:
http://pypi.python.org/pypi/Pillow/1.0
Some background: I've been doing Plone development for the past 5 years or
so, and PIL has always been an
I have been wanting to tackle this for sometime, and finally got around to
it tonight. I've created a friendly fork of PIL called Pillow:
http://pypi.python.org/pypi/Pillow/1.0
Some background: I've been doing Plone development for the past 5 years or
so, and PIL has always been an issue. I
[To the whole list this time, again, for good. Really sorry for the
spam Daniel.]
Semi-related brain dump. It's indeed unclear which issues Pillow is
trying to solve, but PIL has indeed an extremely high amount of them.
First of all, one that bugged me for ever now, is the extremely poor
11 matches
Mail list logo
