Mon Jul 6 14:19:20 GMT 2020
On Mon, 2020-07-06 at 09:57 +0100, Hamish McIntyre-Bhatty via Cygwin-
> On 05/07/2020 23:21, Yaakov Selkowitz wrote:
> > On Fri, 2020-06-26 at 01:49 +0100, Hamish McIntyre-Bhatty via Cygwin-
> > apps wrote:
> > > This email signals my intent to package python3-pillow
> > > (https://pypi.org/project/Pillow) for Cygwin. Pillow is a fork of the
> > > Python Imaging Library.
> > >
> > > I wish to package this because I have found that PyCrust (built with
> > > wxPython) depends on Pillow and won't run without it installed. As
> > > before, my test packages can be found at
> > > https://www.hamishmb.com/files/cygwin-temp/.
> > >
> > > If anyone has feedback I'd appreciate it very much.
> > 1) Source packages are generally named python-*.
> Yes, but the latest build of Pillow doesn't support Python 2 - I feel
> calling it python-pillow would be misleading.
No, this is the naming scheme we've been using for Python packages.
pythonXY-foo: binaries for each supported X.Y version of Python
> > 2) This should be an ITA for python-imaging instead, which has been
> > Pillow-based for a long time.
> The Python imaging library was replaced by Pillow as far as I can tell,
> and seems to have been unmaintained since 2011. Could you give me a link
> to the library you're talking about please?
As I said, our python-imaging packages have been from Pillow for quite
some time. Technically, at this point they should be named python-pil
or the like, but the package name long predates the PIL namespace being
mandatory (not to mention the Pillow fork in general), but I never
renamed the packages to avoid the complications involved therein.
Either way, "pillow" isn't the right name IMO because users don't
"from Pillow import", they "from PIL import".
More information about the Cygwin-apps