From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: Re: Python 2 end-of-life? Date: Wed, 27 Nov 2019 18:35:42 +0100 Message-ID: References: <20191126215145.GA1044@PhantoNv4ArchGx.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40348) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ia1EJ-000263-Sr for guix-devel@gnu.org; Wed, 27 Nov 2019 12:35:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ia1EI-0003Og-Rb for guix-devel@gnu.org; Wed, 27 Nov 2019 12:35:55 -0500 Received: from mail-qk1-x72e.google.com ([2607:f8b0:4864:20::72e]:40695) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ia1EI-0003OH-LG for guix-devel@gnu.org; Wed, 27 Nov 2019 12:35:54 -0500 Received: by mail-qk1-x72e.google.com with SMTP id a137so18423689qkc.7 for ; Wed, 27 Nov 2019 09:35:54 -0800 (PST) In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Konrad Hinsen Cc: Guix Devel Hi Konrad, On Wed, 27 Nov 2019 at 08:56, Konrad Hinsen wrote: > > IOW, a bunch just differ by version -- I wonder how many of the > > packages that drew in old versions could run fine with respective > > latest versions of what they are dependent on? > > That's a very good question! Is it not cheap to replace the python2 dependency by the python3 one and try to locally build? The snippet of code you sent helps to figure out which packages are still using Python2. As you said, some packages will not be updated to Python 3. Let document it in description for example and let provide a rationale explaining why that we put in the manual. > 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. > Guix might well contribute to a long-term improvement of everyone's > habits in this respect, by providing the bird's-eyes view of software > systems that developers and maintainers of individual packages cannot > have. What you describe is just the application of well-known ideas from > software engineering (cleaning up code before it becomes unmaintainable) > to the systems level. Which is possible because Guix turns the systems > level into just another software layer. Agree! :-) All the best, simon