From: Brett Gilio <brettg@posteo.net>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: the upcoming Great Python2 Purge™
Date: Mon, 18 Feb 2019 12:38:35 -0600 [thread overview]
Message-ID: <87va1h3psk.fsf@posteo.net> (raw)
In-Reply-To: <20190218095619.GC7206@macbook41>
Efraim Flashner writes:
> I checked 'guix refresh -l python2' and I got a list of the python2-*
> packages which are leaf packages. I'm not suggesting that we right now
> get rid of them, but it seems to me something worth keeping an eye on.
>
> 'guix package -A ^python2- | wc -l' gave me 737
> the number of leaf python2 packages I found was 222.
>
> This is only a first round; I didn't check to see if we were to remove
> these packages how many more leaf python2 packages we would have.
There are a few leaf packages that are being used to generate the
python3 equivalent. So, maybe we should make a list of leaf packages
that are otherwise safe to be dismissed. Also, what is the status of
somebody deciding to move a lot of these to a channel?
next prev parent reply other threads:[~2019-02-18 18:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-26 9:38 the upcoming Great Python2 Purge™ Efraim Flashner
2018-12-26 12:30 ` Marius Bakke
2018-12-26 13:33 ` add DEPRECATION grace period: " Pjotr Prins
2018-12-27 4:47 ` Leo Famulari
2018-12-27 15:52 ` Alex Vong
2018-12-27 4:50 ` Leo Famulari
2018-12-26 19:47 ` Konrad Hinsen
2018-12-27 4:38 ` Leo Famulari
2018-12-27 14:49 ` Brett Gilio
2019-02-18 9:56 ` Efraim Flashner
2019-02-18 10:16 ` Konrad Hinsen
2019-02-18 10:29 ` Ricardo Wurmus
2019-02-18 11:02 ` Konrad Hinsen
2019-02-18 11:07 ` Ricardo Wurmus
2019-02-18 14:42 ` zimoun
2019-02-18 16:30 ` Konrad Hinsen
2019-02-18 16:54 ` the upcoming Great Python2 Purge�?� ng0
2019-02-18 19:27 ` the upcoming Great Python2 Purge™ zimoun
2019-02-18 18:38 ` Brett Gilio [this message]
2019-02-18 21:39 ` Björn Höfling
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87va1h3psk.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=efraim@flashner.co.il \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.