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.4 is about to EOL in <2 months
Date: Thu, 24 Jan 2019 08:48:54 +0100 [thread overview]
Message-ID: <1548316134.799.3.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Hi, everyone.
Just a quick reminder that Python 3.4 is reaching its end-of-life.
The upstream EOL is set on 2019-03-16 [1], and we will also finally kill
its support for real near that time.
Please also note that a growing number of projects has dropped Python
3.4 support already and requires at least 3.5. Many of us (including
myself) can no longer test 3.4 without getting into ugly downgrades or
dependency conflicts.
If you are still using Python 3.4 with Gentoo packages, please consider
switching to a newer version (or a local solution such as virtualenv)
ASAP.
[1]:https://devguide.python.org/#status-of-python-branches
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next reply other threads:[~2019-01-24 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 7:48 Michał Górny [this message]
2019-03-21 13:38 ` [gentoo-python] Python 3.4 is about to EOL in <2 months Michał Górny
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=1548316134.799.3.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