From: Leo Famulari <leo@famulari.name>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel@gnu.org
Subject: Re: add DEPRECATION grace period: the upcoming Great Python2 Purge™
Date: Wed, 26 Dec 2018 23:47:13 -0500 [thread overview]
Message-ID: <20181227044713.GB2903@jasmine.lan> (raw)
In-Reply-To: <20181226133355.5hqv35f3y5tm3gnk@thebird.nl>
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
On Wed, Dec 26, 2018 at 02:33:55PM +0100, Pjotr Prins wrote:
> A lot of software outside Guix still depends on Python2, for better or
> worse. I don't believe EOL means they are going to drop security
> updates. Leaf packages may well be in use today.
I do think it means that the current Python team at python.org will stop
issuing security updates for Python 2. [0]
Previously, Guido van Rossum said "The way I see the situation for 2.7
is that EOL is January 1st, 2020, and there will be no updates, not even
source-only security patches, after that date. Support (from the core
devs, the PSF, and python.org) stops completely on that date." [1]
Well, Guido is no longer involved with Python, so maybe the situation
has changed. In any case, I think we can expect third parties like Red
Hat to keep maintaining Python 2 for some years, and we can use their
work.
> Is there a way we mark packages as DEPRECATED? I think we should not
> just remove packages without a grace period. Deprecate for, say, 3
> months or even 6 months is the way to do this. A deprecation tag
> should include a time stamp that gives the (planned) removal time.
Not exactly, although there is a 'deprecated-package' procedure that
accepts a replacement package to supersede the deprecated package. It
doesn't do what you suggest.
[0] Already, the status of Python 2 is 'bugfix'. If it reaches "end
of life", the bugfixing activity will presumably cease, although they do
describe another 'security' status that seems lesser than 'bugfix':
https://devguide.python.org/#status-of-python-branches
[1]
https://mail.python.org/pipermail/python-dev/2018-March/152348.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-27 4:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 9:38 the upcoming Great Python2 Purge™ Efraim Flashner
2018-12-26 12:30 ` Marius Bakke
2018-12-26 13:33 ` add DEPRECATION grace period: " Pjotr Prins
2018-12-27 4:47 ` Leo Famulari [this message]
2018-12-27 15:52 ` Alex Vong
2018-12-27 4:50 ` Leo Famulari
2018-12-26 19:47 ` Konrad Hinsen
2018-12-27 4:38 ` Leo Famulari
2018-12-27 14:49 ` Brett Gilio
2019-02-18 9:56 ` Efraim Flashner
2019-02-18 10:16 ` Konrad Hinsen
2019-02-18 10:29 ` Ricardo Wurmus
2019-02-18 11:02 ` Konrad Hinsen
2019-02-18 11:07 ` Ricardo Wurmus
2019-02-18 14:42 ` zimoun
2019-02-18 16:30 ` Konrad Hinsen
2019-02-18 16:54 ` the upcoming Great Python2 Purge�?� ng0
2019-02-18 19:27 ` the upcoming Great Python2 Purge™ zimoun
2019-02-18 18:38 ` Brett Gilio
2019-02-18 21:39 ` Björn Höfling
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181227044713.GB2903@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).