On 2012-10-10 19:31:35 +, Mark Sienkiewicz said:
On 10/10/12 15:07, Alex Clark wrote:
- Pillow started as a packaging fork, but I now consider image code
fixes if they are tracked upstream (by ticket or commit).
Does that mean you are looking for a ticket filed against the old PIL
for
On 2012-10-09 20:26:37 +, Brian Crowell said:
On Tue, Oct 9, 2012 at 3:11 PM, Mark Sienkiewicz wrote:
From what I read of Pillow, they aren't really interested in maintaining a
copy of PIL. Do you mean to fork Pillow, or try to persuade them to let you
help maintain it?
I want to contri
On 2012-10-11 14:30:14 +, Mark Sienkiewicz said:
On 10/10/12 23:12, Alex Clark wrote:
On 2012-10-11 02:57:07 +, Brian Crowell said:
On Wed, Oct 10, 2012 at 8:07 PM, Alex Clark wrote:
No. But maybe a single "Python 3 support" ticket in the relevant branch
(https://bitbucket.org/effbo
On 10/10/12 23:12, Alex Clark wrote:
On 2012-10-11 02:57:07 +, Brian Crowell said:
On Wed, Oct 10, 2012 at 8:07 PM, Alex Clark wrote:
No. But maybe a single "Python 3 support" ticket in the relevant branch
(https://bitbucket.org/effbot/pil-2009-raclette). IIUC, PIL has some Python
support
On 2012-10-11 02:57:07 +, Brian Crowell said:
On Wed, Oct 10, 2012 at 8:07 PM, Alex Clark wrote:
No. But maybe a single "Python 3 support" ticket in the relevant branch
(https://bitbucket.org/effbot/pil-2009-raclette). IIUC, PIL has some Python
support added. One possible scenario is that
On Wed, Oct 10, 2012 at 8:07 PM, Alex Clark wrote:
> No. But maybe a single "Python 3 support" ticket in the relevant branch
> (https://bitbucket.org/effbot/pil-2009-raclette). IIUC, PIL has some Python
> support added. One possible scenario is that we take that code and release
> it.
Do you cons
On 2012-10-10 19:31:35 +, Mark Sienkiewicz said:
On 10/10/12 15:07, Alex Clark wrote:
- Pillow started as a packaging fork, but I now consider image code
fixes if they are tracked upstream (by ticket or commit).
Does that mean you are looking for a ticket filed against the old PIL
for
Within the Plone comunity, Pillow has been the "de facto" flavour of PIL for
several months now. The fact it behaves as expected with
package management (easy_install, PIL), is vital for large
web projects which are based on buildout and expect
Python projects to install properly.
Plone itself is
On 10/10/12 15:07, Alex Clark wrote:
- Pillow started as a packaging fork, but I now consider image code fixes if
they are tracked upstream (by ticket or commit).
Does that mean you are looking for a ticket filed against the old PIL for each
of the python 3 modifications? If not, how does
On 2012-10-10 16:00:40 +, Alex Clark said:
On 2012-10-09 20:26:37 +, Brian Crowell said:
On Tue, Oct 9, 2012 at 3:11 PM, Mark Sienkiewicz wrote:
From what I read of Pillow, they aren't really interested in maintaining a
copy of PIL. Do you mean to fork Pillow, or try to persuade the
On 2012-10-09 20:26:37 +, Brian Crowell said:
On Tue, Oct 9, 2012 at 3:11 PM, Mark Sienkiewicz wrote:
From what I read of Pillow, they aren't really interested in maintaining a
copy of PIL. Do you mean to fork Pillow, or try to persuade them to let you
help maintain it?
I want to contri
On Tue, Oct 9, 2012 at 3:11 PM, Mark Sienkiewicz wrote:
> From what I read of Pillow, they aren't really interested in maintaining a
> copy of PIL. Do you mean to fork Pillow, or try to persuade them to let you
> help maintain it?
I want to contribute code that would make Pillow Python 3-capable
On 10/09/12 16:02, Brian Crowell wrote:
On Tue, Oct 9, 2012 at 1:41 PM, Mark Sienkiewicz wrote:
So, how do you get people to know about and use your package?
Well, that's why I asked the Debian package maintainer first. He
pointed me here. He wasn't exactly clear, but he seemed interested in
P
On Tue, Oct 9, 2012 at 1:41 PM, Mark Sienkiewicz wrote:
> So, how do you get people to know about and use your package?
Well, that's why I asked the Debian package maintainer first. He
pointed me here. He wasn't exactly clear, but he seemed interested in
Pillow as the source of a Python 3 port sp
On 10/09/12 00:51, Brian Crowell wrote:
Yes, that seems to me to be the main trouble. Anything done to the
Python source will break compatibility with code before 2.6. I'm sure
that's why it looks like PIL has been ported to Python 3 several
times, but none of them stuck.
How do other developers
I'm not a dev, just a user. Adding my 2 cents.
I'd say having 1.1.7 around for Python 2.5 seems sufficient. 2.5 is
old, 1.1.7 is stable, it should fit most use cases there.
I'd much rather drop 2.5 support and gain 3.x for PIL. Keeping 2.6
support would be a very good thing. Even though 2.6 i
Am 09.10.2012, 06:51 Uhr, schrieb Brian Crowell :
How do other developers feel about that? Maybe letting old PIL 1.1.7
take care of anyone using 2.5/2.6 or older, and focusing on 2.6/2.7
and up? Or perhaps maintaining a separate branch with Python 3 code?
2.6 tends to have fairly good support
On Mon, Oct 8, 2012 at 6:56 PM, Hajime Nakagami wrote:
> That's most import bug(?) is only support Python2.7 and Python3.3
>
> If you need widely version support, Probabry use 2to3 approach.
Yes, that seems to me to be the main trouble. Anything done to the
Python source will break compatibility
On 10/8/2012 4:56 PM, Hajime Nakagami wrote:
Hi Brian, and all
I'm trying to suport python3.3 and python2.7 by one source
https://github.com/nakagami/Pillow
(please checkout py33py27 branch)
It seems to work at gif, jpeg and png. But other many image format
still not work.
That's most import b
Hi Brian, and all
I'm trying to suport python3.3 and python2.7 by one source
https://github.com/nakagami/Pillow
(please checkout py33py27 branch)
It seems to work at gif, jpeg and png. But other many image format
still not work.
That's most import bug(?) is only support Python2.7 and Python3.3
Hi. I'm interested in helping bring PIL to Python 3.
I contacted Matthias Klose, the package maintainer for PIL, to see
which codebase he thought would be best to do that on, and he pointed
me to Pillow, so I'm here to ask about what's been done so far for
Python 3 support and what I could do.
I
21 matches
Mail list logo
