From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: [gentoo-python] Python 3.7 is in!
Date: Mon, 16 Jul 2018 22:04:33 +0200 [thread overview]
Message-ID: <1531771473.1439.7.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
Hi, everyone.
I've just enabled Python 3.7 compatibility in the initial set
of packages (~135 dependencies of setuptools). Now that the hardest
part of the depgraph is done, you can start adding 3.7 support to your
packages.
As usual, I'd like to kindly ask you to enable tests in your packages
and make sure that they work correctly. I would like to note that I've
also updated the documentation on running tests [1]. gpyutils are
running 3.6→3.7 reports [2] for a few days now. However, the graphs are
currently disabled as the number of packages is too great for graphviz
to handle sanely.
[1]:https://wiki.gentoo.org/wiki/Project:Python/Tests
[2]:https://qa-reports.gentoo.org/output/gpyutils/36-to-37.txt
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
reply other threads:[~2018-07-16 20:04 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=1531771473.1439.7.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
/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