From: Leo Famulari <leo@famulari.name>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: the upcoming Great Python2 Purge™
Date: Wed, 26 Dec 2018 23:38:41 -0500 [thread overview]
Message-ID: <20181227043841.GA5572@jasmine.lan> (raw)
In-Reply-To: <20181226093812.GR2581@macbook41>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Wed, Dec 26, 2018 at 11:38:12AM +0200, Efraim Flashner wrote:
> We're now about a year out from the official EOL for python2 (Jan 1,
> 2020). So far we've been not adding python2 variants of packages that
> are new unless they're actually needed for something. Do we want to
> start removing python2 packages when updating other packages if they are
> leaf packages?
This was previously discussed here:
https://lists.gnu.org/archive/html/guix-devel/2018-06/msg00237.html
That discussion didn't go very far. As you mentioned, the consensus
seemed to be that we 1) relax the policy of always providing both Python
2 and 3 packages and 2) we'll act when we need to.
My opinion is that we should remove Python 2 packages after the upstream
EOL announcement if they are causing trouble somehow.
But I don't think we need to remove them en masse. We offer many other
packages that are basically abandoned upstream, so I think it will be
okay to keep the Python 2 packages as long as there are no bugs or if
they are maintained somehow.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-27 4:38 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181227043841.GA5572@jasmine.lan \
--to=leo@famulari.name \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.