unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Python 2 end-of-life?
Date: Fri, 29 Nov 2019 05:42:39 -0800	[thread overview]
Message-ID: <20191129134239.GA77005@PhantoNv4ArchGx.localdomain> (raw)
In-Reply-To: <CAJ3okZ2kpKxTJzyYeLu0Go+XW1qHS-rbPqjQ3XB-4Gt-AYaDvQ@mail.gmail.com>

Hi zimoun,

On +2019-11-29 12:41:43 +0100, zimoun wrote:
> Hi Bengt,
> 
[...]
> 
> > > > That's yet another question: could we patch the upstream code to replace
> > > > Python by something else that's more convenient for Guix. That may
> > > > actually be a worthwhile approach to reduce software bloat in Guix,
> > > > but it also shifts some of the maintenance burden from upstream to Guix.
> > >
> > > It does not appear to me a reasonable approach.
> >
> > If it could be an automated patch substitution of a pure guix function that
> > will pass the same well-designed test suite as the python function it replaces,
> > then I think it is entirely reasonable. We are not asking upstream to do anything,
> > other than providing a well-designed test suite that will serve themselves well.
> 
> Please show me the code and I will change my mind about the
> "reasonable approach". :-)
> 
> And what do we win? More reproducibility? More bootstrappability?
>

https://en.wikiquote.org/wiki/C._A._R._Hoare#The_Emperor's_Old_Clothes

The first quote in particular ;-)

> 
> All the best,
> simon

-- 
Regards,
Bengt Richter

  reply	other threads:[~2019-11-29 13:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 15:39 Python 2 end-of-life? zimoun
2019-11-21 11:46 ` zimoun
2019-11-21 12:01   ` Konrad Hinsen
2019-11-26 16:51     ` Konrad Hinsen
2019-11-26 17:50       ` Hartmut Goebel
2019-11-26 18:55         ` ng0
2019-11-27  8:28         ` Konrad Hinsen
2019-11-27 17:41           ` zimoun
2019-11-26 21:51       ` Bengt Richter
2019-11-27  7:56         ` Konrad Hinsen
2019-11-27 17:35           ` zimoun
2019-11-29  6:07             ` Bengt Richter
2019-11-29  7:38               ` Konrad Hinsen
2019-11-29 12:12                 ` zimoun
2019-11-29 11:41               ` zimoun
2019-11-29 13:42                 ` Bengt Richter [this message]
2019-11-29 14:12                   ` zimoun
2019-11-29 22:16                     ` Bengt Richter
2019-11-27 17:28         ` zimoun
2019-11-27 17:43           ` Ricardo Wurmus
2019-11-29  6:54           ` Bengt Richter
2019-11-29 11:55             ` zimoun
2019-11-28 14:40       ` Konrad Hinsen
2019-11-28 15:50         ` Hartmut Goebel
2019-11-28 18:22           ` zimoun
2019-11-21 17:28   ` Alex Griffin

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=20191129134239.GA77005@PhantoNv4ArchGx.localdomain \
    --to=bokr@bokr.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).