From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Python 2 retirement — what should Guix do?
Date: Sat, 16 Jun 2018 22:42:43 +0200 [thread overview]
Message-ID: <20180616204243.xx2b4qygntiminfl@thebird.nl> (raw)
In-Reply-To: <20180616183055.kal6urc6srrn7ikl@abyayala>
The move from Python2 to Python3 will go into the history books as one
hugely mismanaged transition - call it a first order screw up. The
cost to the community is enormous, if I go by the hours I personally
already spent on managing the issue! And that just for the sake of a
few (minor) syntax changes and a new API for C extensions.
Not even the Ruby guys fucked up so badly with the transition to 2.0!
And that was bad enough. Especially the change in behaviour of Proc.
Guix is actually one of the best tools to manage the transition. I
love it for that. I don't think we should keep supporting both Python
2 and 3 versions of modules by default when the time comes. People
will do that when they need to. I will. But we can certainly ease the
transition at little cost (to us).
So, Leo, +1 from me.
Pj.
next prev parent reply other threads:[~2018-06-16 20:42 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 [this message]
2018-06-16 21:08 ` Pjotr Prins
2018-06-16 21:01 ` Ricardo Wurmus
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
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=20180616204243.xx2b4qygntiminfl@thebird.nl \
--to=pjotr.public12@thebird.nl \
--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 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).