From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Release 1.2.1: Remove 31 Python 2 packages
Date: Sat, 13 Mar 2021 20:03:55 -0500 [thread overview]
Message-ID: <87ft0ytukk.fsf@gmail.com> (raw)
In-Reply-To: <86r1kmbsz1.fsf@gmail.com> (zimoun's message of "Wed, 10 Mar 2021 22:26:42 +0100")
Hi Simon,
zimoun <zimon.toutoune@gmail.com> writes:
> Hi,
>
> Using “guix weather --display-missing” at commit 6bed29b, I have
> identified these 31 Python 2 packages to remove:
>
> python2-arrow
> python2-cairocffi
> python2-cairocffi
> python2-dulwich
> python2-fido2
> python2-flask
> python2-flask-babel
> python2-flask-htmlmin
> python2-flask-login
> python2-flask-multistatic
> python2-flask-wtf
> python2-furl
> python2-graphql-core
> python2-httpbin
> python2-ipykernel
> python2-ipyparallel
> python2-ipython
> python2-ipython-cluster-helper
> python2-ipywidgets
> python2-jupyter-console
> python2-mpd2
> python2-mutagen
> python2-nbxmpp
> python2-pyfakefs
> python2-rq
> python2-sh
> python2-stem
> python2-tables
> python2-utils
> python2-widgetsnbextension
> python2-wsgiproxy2
> python2-yubikey-manager
>
>
> They do not build. The Python 3 variant builds or does not exist.
>
> Last, “guix refresh -l <pkg>” is fine.
>
>
> Any objection?
It's hard objecting to removing Python 2 packages, with Python 2 having
been EOL since 2020. In my opinion, some exceptions could apply, if
something provides unique value that cannot be substituted. I guess
these are increasingly rare...
In the end though, the Python 2 packages must go, so I think it's not
unreasonable to remove the broken ones to start. Someone finding the
packages important enough could fix them and publish them in a separate
Python 2 channel.
So, no objections here.
Maxim
next prev parent reply other threads:[~2021-03-14 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 21:26 Release 1.2.1: Remove 31 Python 2 packages zimoun
2021-03-14 1:03 ` Maxim Cournoyer [this message]
2021-03-15 16:02 ` zimoun
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=87ft0ytukk.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).