all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Python 2 retirement — what should Guix do?
Date: Sat, 16 Jun 2018 23:01:31 +0200	[thread overview]
Message-ID: <87h8m25tuc.fsf@elephly.net> (raw)
In-Reply-To: <20180616180118.GA9585@jasmine.lan>


Hi Leo,

> Presumably, Python 2 will be maintained by some third parties for quite
> a while after 2020.

If that is so, it’s probably fine to keep a “python2” package.

> Personally, I think our set of Python packages is relatively hard to
> maintain. There is a lot of brittle code in there. I'd be happy to drop
> our policy that Python libraries have both Python 2 and 3 packages by
> default.

I agree.  My preference is to build Python 2 packages only when
absolutely needed by another package.

It’s possible that this will be a non-negligible number of packages
(some bioinfo tools developed in 2018 come to mind…), but I don’t want
us to artificially extend the lifespan of an unmaintained language.

--
Ricardo

  parent reply	other threads:[~2018-06-16 21:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16 18:01 Python 2 retirement — what should Guix do? Leo Famulari
2018-06-16 18:30 ` Nils Gillmann
2018-06-16 20:42   ` Pjotr Prins
2018-06-16 21:08     ` Pjotr Prins
2018-06-16 21:01 ` Ricardo Wurmus [this message]
2018-06-17 21:15   ` Ludovic Courtès
2018-06-18  7:45     ` Pjotr Prins
2018-06-17 14:13 ` Konrad Hinsen

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=87h8m25tuc.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.