From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python3-pillow
Date: Mon, 11 Jan 2021 04:59:29 +0100 [thread overview]
Message-ID: <5f9f57c8-84dc-f661-fbf7-896f5ae88df6@gmail.com> (raw)
In-Reply-To: <62f31bf7cbc241794d34572f5a1cf0c694d65b39.camel@cygwin.com>
On 06.07.2020 16:19, Yaakov Selkowitz wrote:
> On Mon, 2020-07-06 at 09:57 +0100, Hamish McIntyre-Bhatty via Cygwin-
> apps wrote:
>> 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:
>>> 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".
>
> --
> Yaakov
for the record, I removed python3-pillow from cygwin-pkg-maint.
better late than never
Regards
Marco
prev parent reply other threads:[~2021-01-11 3:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 0:49 Hamish McIntyre-Bhatty
2020-07-04 12:01 ` Hamish McIntyre-Bhatty
2020-07-04 15:37 ` Marco Atzeri
2020-07-05 22:21 ` Yaakov Selkowitz
2020-07-06 8:57 ` Hamish McIntyre-Bhatty
2020-07-06 14:19 ` Yaakov Selkowitz
2021-01-11 3:59 ` Marco Atzeri [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f9f57c8-84dc-f661-fbf7-896f5ae88df6@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).