From: Maxime Devos <maximedevos@telenet.be>
To: zimoun <zimon.toutoune@gmail.com>, "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 11:36:29 +0200 [thread overview]
Message-ID: <794901deeac0d8360dc8d8d8a05a6fcea528d581.camel@telenet.be> (raw)
In-Reply-To: <86k09zil16.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]
zimoun schreef op do 02-06-2022 om 09:25 [+0200]:
> 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? :-)
I didn't know that. I guess we should have said back then ‘no adding
new python2 packages because of the grace period, only updates’ and
announced and documented the policy? (assuming this argument)
> 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. [...]
> 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.
I agree that it is a sudden transition for a user that does not follow
upstream news and that it only is a smooth transition for people in the
know. It's a bit a matter of perspective I guess? Agreed with more
explicit communication. And maybe Guix could have done more, e.g. by
helping upstream with porting to python3.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-02 9:37 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
2022-06-02 9:36 ` Maxime Devos [this message]
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=794901deeac0d8360dc8d8d8a05a6fcea528d581.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=maxim.cournoyer@gmail.com \
--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).