From: "Alex Griffin" <a@ajgrf.com>
To: guix-devel@gnu.org
Subject: Re: Python 2 end-of-life?
Date: Thu, 21 Nov 2019 17:28:43 +0000 [thread overview]
Message-ID: <ea454dda-892b-4361-b5ba-2b53c31adab7@www.fastmail.com> (raw)
In-Reply-To: <CAJ3okZ3jED18YLH0KZ1V9=JfeCYh00uHPg+=TiNDx2r5th46Xg@mail.gmail.com>
On Thu, Nov 21, 2019, at 11:46 AM, zimoun wrote:
> What do you do?
> Do we deprecate the python2 packages? If yes, what would be the
> schedule? If no, do we move all the python2 packages to a
> python2-xyz.scm file?
> Do we do nothing? Based on what rationale?
I think a good place to start is by just filing bugs against packages that rely on Python 2, saying that they face removal once Python 2 is EOL. As Konrad pointed out though, not every package necessarily needs to support Python 3. I think there can probably be exceptions for packages that do not add much security risk or maintenance work.
Red Hat will continue providing security fixes to Python 2 for several more years. PyPy will also continue to support Python 2 indefinitely, so packaging that and making it an option in python-build-system may be an option for some packages.
--
Alex Griffin
prev parent reply other threads:[~2019-11-21 17:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 15:39 Python 2 end-of-life? zimoun
2019-11-21 11:46 ` zimoun
2019-11-21 12:01 ` Konrad Hinsen
2019-11-26 16:51 ` Konrad Hinsen
2019-11-26 17:50 ` Hartmut Goebel
2019-11-26 18:55 ` ng0
2019-11-27 8:28 ` Konrad Hinsen
2019-11-27 17:41 ` zimoun
2019-11-26 21:51 ` Bengt Richter
2019-11-27 7:56 ` Konrad Hinsen
2019-11-27 17:35 ` zimoun
2019-11-29 6:07 ` Bengt Richter
2019-11-29 7:38 ` Konrad Hinsen
2019-11-29 12:12 ` zimoun
2019-11-29 11:41 ` zimoun
2019-11-29 13:42 ` Bengt Richter
2019-11-29 14:12 ` zimoun
2019-11-29 22:16 ` Bengt Richter
2019-11-27 17:28 ` zimoun
2019-11-27 17:43 ` Ricardo Wurmus
2019-11-29 6:54 ` Bengt Richter
2019-11-29 11:55 ` zimoun
2019-11-28 14:40 ` Konrad Hinsen
2019-11-28 15:50 ` Hartmut Goebel
2019-11-28 18:22 ` zimoun
2019-11-21 17:28 ` Alex Griffin [this message]
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=ea454dda-892b-4361-b5ba-2b53c31adab7@www.fastmail.com \
--to=a@ajgrf.com \
--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).