From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Raghav Gururajan <rg@raghavgururajan.name>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: 5c8369d6c1 gnu: Add python2-twodict ?
Date: Tue, 29 Jun 2021 00:04:57 -0400 [thread overview]
Message-ID: <87tulhuxhy.fsf@gmail.com> (raw)
In-Reply-To: <b7088906-52b3-2f9a-a5b2-6df9dbca4b0a@raghavgururajan.name> (Raghav Gururajan's message of "Mon, 28 Jun 2021 15:07:54 -0400")
Hello Raghav,
Raghav Gururajan <rg@raghavgururajan.name> writes:
[...]
>> Python 2 is EOL since a long time now
>
> Ah I see. I didn't know that.
>
>> package youtube-dl-gui is from 2018 and the release 0.4 from 2017.
>> Well, I do not know if it is worth to update such package. :-)
>
> I first thought the same, but it seems the app is feature complete and
> no additional changes.
>
> That said, considering deprecation of python2 by python upstream, this
> package should have been ported to python3.
>
>> I propose to deprecate this package because it will be removed soon or later.
> Yeah, since python2 is deprecated. We could deprecate
> youtube-dl-gui. Should we do this is as a batch, removing all python2
> packages?
Perhaps youtube-dl-gui could be removed along the python2 *leaf*
packages that are orphaned as a result.
The consensus for Python 2 packages is that they have to go, but that
it's OK for their removal to be gradual. They tend to break because
upstream often stops supporting Python 2 and can thus be phased out
naturally when it happens this way.
It's a good exercise to try to "free" important packages from any Python
2 appearing in their closure.
Thanks,
Maxim
next prev parent reply other threads:[~2021-06-29 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 14:23 5c8369d6c1 gnu: Add python2-twodict ? zimoun
2021-06-28 19:07 ` Raghav Gururajan
2021-06-29 4:04 ` Maxim Cournoyer [this message]
2021-06-29 9:00 ` 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=87tulhuxhy.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rg@raghavgururajan.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).