From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: cygwin-announce@cygwin.com
Subject: Test: python-imaging 7.2.0-1
Date: Tue, 21 Jul 2020 14:55:18 +0100 [thread overview]
Message-ID: <AM0PR05MB4898773A1372DDA4EE5929A8E7780@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1287 bytes --]
Version 7.2.0-1 of "python-imaging" has been uploaded as a test package.
python-imaging (aka Pillow) is a fork or the Python Imaging Library (PIL).
This update provides the following packages:
python-imaging (the source package)
python-imaging-debuginfo
python36-imaging, python36-imaging-tk
python37-imaging, python37-imaging-tk
python38-imaging, python38-imaging-tk
This update brings a builds for newer versions of Python, and is much
newer than the currently stable build for Cygwin. I have had no issues
using this so far, and will mark as stable in about a week's time if no
issues are reported. Both positive and negative feedback will be
appreciated.
*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:
cygwin-announce-unsubscribe-you=yourdomain.com <at> cygwin.com
If you need more information on unsubscribing, start reading here:
https://sourceware.org/lists.html#unsubscribe-simple
Please read *all* of the information on unsubscribing that is available
starting at this URL.
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3237 bytes --]
[-- Attachment #1.1.3: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2020-07-21 13:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AM0PR05MB4898773A1372DDA4EE5929A8E7780@AM0PR05MB4898.eurprd05.prod.outlook.com \
--to=hamishmb@live.co.uk \
--cc=cygwin-announce@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).