all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: the upcoming Great Python2 Purge™
Date: Wed, 26 Dec 2018 23:50:17 -0500	[thread overview]
Message-ID: <20181227045017.GB5572@jasmine.lan> (raw)
In-Reply-To: <87pnto8o76.fsf@fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 2049 bytes --]

On Wed, Dec 26, 2018 at 01:30:53PM +0100, Marius Bakke wrote:
> Efraim Flashner <efraim@flashner.co.il> writes:
> > 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?
> 
> I think it's okay to start removing "leaf" Python 2 packages.  In most
> cases they were probably never used anyway, or the dependents have
> transitioned to their Python 3 counterparts.
> 
> We'll probably break some channels, but I'm sure our users won't have
> any difficulties adding them back to their own channels if need be.

If we were to start removing Python 2 packages, I like Pjotr's
suggestion that we offer a lengthy grace period to help people set up
some channels to support their work. We don't need to always do this
sort of thing but, in this case, it will be good practice for everyone
involved, and the change is large and well-publicized.

My opinion is that we don't need to start removing them before 2020 and,
even after that, we may choose to use a 3rd-party Python 2 distribution
from someone like Red Hat. Of course, as always, it depends on whether
or not any Guix developers are willing to do the work.

> On a related note, we also have a number of [Python 3] packages that
> have been failing to build for a long time.  Some of these are trivial,
> i.e. what "guix import" produces.
> 
> It would be good to get rid of those as well, as the would-be user is
> much better off starting from "guix import" instead of first getting
> disappointed by the Guix package and then having to go through all the
> trouble of submitting a patch.
> 
> Should we have some sort of policy or threshold for when to remove such
> packages?  Maybe after 3-6 months?

Yes, I agree, there must be some point where we remove packages that
simply don't work at all.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-12-27  4:50 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181227045017.GB5572@jasmine.lan \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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.
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.