From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Python 2 retirement — what should Guix do?
Date: Sat, 16 Jun 2018 14:01:18 -0400 [thread overview]
Message-ID: <20180616180118.GA9585@jasmine.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
In 2020, Python 2 will no longer be supported by the Python team. [0]
To quote Guido van Rossum, "The way I see the situation for 2.7 is that
EOL is January 1st, 2020, and there will be no updates, not even
source-only security patches, after that date. Support (from the core
devs, the PSF, and python.org) stops completely on that date." [1]
In Guix we aim to offer software that is safe to use, which typically
means "maintained".
Presumably, Python 2 will be maintained by some third parties for quite
a while after 2020.
I wonder, what should Guix do?
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.
[0]
https://legacy.python.org/dev/peps/pep-0373/
[1]
https://mail.python.org/pipermail/python-dev/2018-March/152348.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-06-16 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 18:01 Leo Famulari [this message]
2018-06-16 18:30 ` Python 2 retirement — what should Guix do? 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
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=20180616180118.GA9585@jasmine.lan \
--to=leo@famulari.name \
--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 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).