From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Python 2 retirement — what should Guix do?
Date: Sun, 17 Jun 2018 23:15:36 +0200 [thread overview]
Message-ID: <87lgbdjerr.fsf@gnu.org> (raw)
In-Reply-To: <87h8m25tuc.fsf@elephly.net> (Ricardo Wurmus's message of "Sat, 16 Jun 2018 23:01:31 +0200")
Hello,
Ricardo Wurmus <rekado@elephly.net> skribis:
> I agree. My preference is to build Python 2 packages only when
> absolutely needed by another package.
“python2-” packages are mostly a convenience for users who’d like to use
them directly. For applications, ‘package-with-python2’ takes care of
“converting” complete DAGs to Python 2, so those “python2-” packages
don’t matter much.
It seems too early to get rid of everything Python 2, as Konrad
suggested.
Softening the policy to add “python2-” packages sounds like a good way
to move forward. For new packages, it’s quite simply: just don’t
provide the “python2-” variant unless it’s required. For existing
packages, it seems trickier though. Which packages would we remove and
when?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-06-17 21:15 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
2018-06-17 21:15 ` Ludovic Courtès [this message]
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
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=87lgbdjerr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).