unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Maxime Devos" <maximedevos@telenet.be>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Merging the purge-python2-packages branch
Date: Thu, 02 Jun 2022 09:25:57 +0200	[thread overview]
Message-ID: <86k09zil16.fsf@gmail.com> (raw)
In-Reply-To: <9ee43bfdcfdc7f6e0b2fa2318f2c9bc32a715701.camel@telenet.be>

On Wed, 01 Jun 2022 at 22:30, Maxime Devos <maximedevos@telenet.be> wrote:

>> (from [0])
>> Sunsetting Python 2
>> [...]
>> We did not want to hurt the people using Python 2. So, in 2008, we
>> announced that we would sunset Python 2 in 2015,
>
> This is a 5 year grace period, which is already a lot of weeks.
> Futhermore, this has even been extended for five additional years:

Following this argument, the question is therefore: why Python 2
packages had been included in Guix in the first place since most
inclusions had already been post this grace period? :-)


> That said, I suppose it would have been better to also repeat the
> message about the grace period on the blog, channel news and info-guix
> (and maybe on IRC too, why not) as you seem to suggest, for people that
> follow distro news but not upstream news, given the large impact (many
> python2 packages)?

I personally do not follow all the upstream code that I run.  I trust
the distro for that.  I guess most people follow distro news for most of
the things they basically run and install from their disto.  I would be
interested to know how many people who use pandoc also follow GHC
development, who use unison and also follow OCaml, who use VLC and
follow GCC, etc. Who used ’wicd’ and also followed Python.

Well, it is off-topic. :-)

To be honest, I am also surprised by the answers trying to justify what
appears to me a breakage of what a distro means.  Maybe my feelings are
wrong, from my point of view, Guix is currently at a crossroad: people
outside the hobbyist’s circle are starting to run Guix in production, or
at least they are starting to think about it.  By doing sudden
transition, we appear abrupt as a distro and the message between the
lines is «Guix is not reliable as a distro».  All such big transition is
difficult whatever the distro [1,2,3].  The aim of a distro is to smooth
user transition, IMHO, which means communicate explicitly for preparing.

Do not take me wrong, I am not making a case for this Python 2 purge.

Now, many Python 2 is gone from Guix.  Despite my concerns, I am really
happy by this achievement and I am very grateful to Maxim for making it
happen.  For having done some janitor tasks in Guix, I know how tedious
this job can be and I am thankful for the heavy and not-fun work that
Maxim did.

In short, I have an opinion for the path at this crossroad and using
this Python 2 purge as example, I am trying to gently express it.


Cheers,
simon

1: <https://wiki.debian.org/Python/2Removal>
2: <https://fedoraproject.org/wiki/FinalizingFedoraSwitchtoPython3>
3: <https://www.gentoo.org/support/news-items/2020-09-28-python-2-7-cleanup.html>


  reply	other threads:[~2022-06-02  7:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 13:25 Merging the purge-python2-packages branch Maxim Cournoyer
2022-05-30 15:18 ` zimoun
2022-05-30 15:32   ` Maxim Cournoyer
2022-05-30 16:49     ` zimoun
2022-05-31  7:39       ` Reza Housseini
2022-05-31 19:07       ` Maxim Cournoyer
2022-05-31 20:54         ` zimoun
2022-06-01 16:21           ` Ludovic Courtès
2022-06-01 19:51             ` zimoun
2022-06-01 20:30               ` Maxime Devos
2022-06-02  7:25                 ` zimoun [this message]
2022-06-02  9:36                   ` Maxime Devos
2022-06-02 14:04               ` Ludovic Courtès

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=86k09zil16.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=maximedevos@telenet.be \
    /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).