Folks,
I'm trying to mentally prepare for adding Python 3 support to Pillow
before PyCon 2013. To do so, I plan to review the work that has been
done here:
- https://github.com/fluggo/Pillow
Then merge and release.
Until this point, we've been attempting to track changes via "upstream"
tickets in the hope that one day there'd be a new PIL release and we'd
stop Pillow development. However I now suspect that the more likely
scenario is that we will have to declare at some point that Pillow is
"the unfriendly PIL fork", meaning that we will not continue to track
changes in Pillow along with the "upstream" changes in PIL.
Does this sound reasonable? I think the "best" time to do this would be
with the addition of Python 3 support to Pillow, along with a
corresponding significant release number change e.g. "Pillow 2.0.0 (now
with Python 3 support)"
Of course, we could consider Python 3 support as another change to
track upstream with PIL. But quite frankly, I'm tired of the additional
maintenance burden, and would now prefer to simply encourage bug fixes
and releases without the additional task of being "friendly" to PIL.
Thoughts?
Alex
--
Alex Clark ยท https://www.gittip.com/aclark4life/
_______________________________________________
Image-SIG maillist - Image-SIG@python.org
http://mail.python.org/mailman/listinfo/image-sig
