From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id cMLBJEHdE2ClNAAA0tVLHw (envelope-from ) for ; Fri, 29 Jan 2021 10:02:41 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id YDVtIEHdE2B2DQAAbx9fmQ (envelope-from ) for ; Fri, 29 Jan 2021 10:02:41 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 239299402B1 for ; Fri, 29 Jan 2021 10:02:41 +0000 (UTC) Received: from localhost ([::1]:39518 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l5Qbw-0007Lb-0E for larch@yhetil.org; Fri, 29 Jan 2021 05:02:40 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:51208) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l5Qbi-0007LH-DX for guix-devel@gnu.org; Fri, 29 Jan 2021 05:02:26 -0500 Received: from mail-qk1-x72b.google.com ([2607:f8b0:4864:20::72b]:42705) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l5Qbg-0007Up-IA for guix-devel@gnu.org; Fri, 29 Jan 2021 05:02:26 -0500 Received: by mail-qk1-x72b.google.com with SMTP id l27so8145515qki.9 for ; Fri, 29 Jan 2021 02:02:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0u2mgMotuj9YCo4ZvyrjwkFet3I9L2QMLF2hXn016i8=; b=FquyNUmD3srTck65maTjbc30RSQEZtwfJu6ssthGV8haYMP/cEX1UtG4n6bA3PYeaE kUDrmv+CKQHforQ5P7zNGskFIJc0qPUj6m7bqrHP6HqLP0WpX/+fbzpgu1fC54F0GHw1 FdQZ4SSJWDgN3Jdmn1vQYrQq0YS4IGYrqe+E/mMMZqoGveJwpOnpqZDeKL+gTuIlWhGY VbwNaRSpSXM9vYcYnltdDhETXpziuiQOgrduKUnT5wHoRv+rmq4j4EYIs+jJaaZNttlb /mHOMrXvkarSMM/CVE+Ik5GbjDJ8nTW+uXILHwPFPqwIf4ItGsvVVxIwPmeAnApgp4O4 KIFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0u2mgMotuj9YCo4ZvyrjwkFet3I9L2QMLF2hXn016i8=; b=q2K42Y7Mnoq2rFP93YQnXGrmV3L3byE9v01fSgiqrf10RobephF5J2jmmTFARIW0qF tD8MMSgnfA8ANqoeCQSlCOSFv3KMUIKLelb2Qpced0Ip9SZ5NvjoLEfpf3bzWAU3+lIA fymG+7WrL8WsVoHwVmuGBG1UlKzug1StU1S1T5s5EKdmDxRDfxvFqI4gdvNvbKtLidDt J2ZefVIhluFTUYGTXVwO+H2P3vOCUNoXzcOkVqlh5HSN5U9wazkoaFWEdNhbdGOKo1rN BXgbkxQtArFtDBm5B6cgOgxfjIvQuMeW9ANyrbl/xIlb8x5MtvB8jMNfSdSH2QIRAMaT G0Eg== X-Gm-Message-State: AOAM531e130II/Nylh4+gmJ1pG8wnB358DDGmC3UJ4DJyNXJ2HnsMom9 MyfKtTKzPqAVWm9raQXaroNTROICcMzzXQ/xsgE= X-Google-Smtp-Source: ABdhPJzjxx+bv2AchcHSOWVOnua3N8jIST/d7xavWH9fHbq6LU9BU/Zjw8lRhL9amxT+A5Zy9pz7Ka7T+4c4ffU0bns= X-Received: by 2002:a37:4fd1:: with SMTP id d200mr3387868qkb.201.1611914540579; Fri, 29 Jan 2021 02:02:20 -0800 (PST) MIME-Version: 1.0 References: <86pn1pgf7z.fsf@gmail.com> <87pn1oxv0m.fsf@gmail.com> In-Reply-To: <87pn1oxv0m.fsf@gmail.com> From: zimoun Date: Fri, 29 Jan 2021 11:02:09 +0100 Message-ID: Subject: Re: Python 2 EOL starts to break packages To: Maxim Cournoyer Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=2607:f8b0:4864:20::72b; envelope-from=zimon.toutoune@gmail.com; helo=mail-qk1-x72b.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Guix Devel Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: "Guix-devel" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.05 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=FquyNUmD; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of guix-devel-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=guix-devel-bounces@gnu.org X-Migadu-Queue-Id: 239299402B1 X-Spam-Score: -3.05 X-Migadu-Scanner: scn1.migadu.com X-TUID: 97VLjuHLpg1r HI Maxim, Thanks for your answer. On Fri, 29 Jan 2021 at 04:49, Maxim Cournoyer wrote: > zimoun writes: > Whenever I update a Python package that breaks its Python 2 variant, I > look at the dependencies of those variants with 'guix refresh -l > python2-something'. If all the dependents are purely python2 variants > themselves, then I proceed to remove them all from the package > collection. If instead some non-python2 variant package > depends on it, I research if that package could be updated to make it > Python 3 compatible. If yes, then problem solved. Otherwise we need to > ping upstream and keep it for a little longer before it gets removed. By "keep it for a little longer", do you mean update the Python 3 version and explicitly define the Python 2 variant ? Or do you mean do not update at all? In other words, should 3142daccbe be reverted? Or should 3142daccbe keep as it is and the variant 'python2-setuptools' defined explicitly with the previous version? Noting that people submitting and reviewing patches should both apply your methodology. Otherwise, the janitor work is more burden. Contrary to what I am proposing, i.e., move all the python2-* variants inside a specific module, where the janitor work can be done asynchronously: open this module and address package one after the other, mainly once a while by batch. Instead of greping, etc. I can tell you by janitoring Bioconductor packages that grepping becomes really annoying when you address more packages than a child is able to count. ;-) In other words, I am proposing to separate update and janitor with an easier janitor task. Well, all are fine with me. The aim of my email is simply to roughly agree on a "way" to collectively ease this boring task. > The python2-behave-web-api is not a concern (there's an existing > python-behave-web-api package), but the others are. There's an issue > about syncthing-gtk reliance on Python 2 at > https://github.com/kozec/syncthing-gtk/issues/568. For grocsvs I've > just commented at https://github.com/grocsvs/grocsvs/issues/6. If the > upstream are not willing to budge, the packages can be removed after a > grace period (6 months, I'd say). Just to fix the idea, the last release of syncthing-gtk is from 4 Aug 2019 and the last commit in master from 30 Oct 2019. The issue you mention is from 30 Nov 2020 but the real first one is #487 [1] from 22 Oct 2018 and mentioning a port to Python 3 by Debian folks [2] (not tried the status). Hum, the 6 months grace period is far beyond. ;-) (I am not asking any remove.) And I guess your are Apteryks that asked to reopen the issue of grocsvs. :-) Well, since this package is Bioinformatics, I can tell you that it will not be ported, another story. However, this Python 2 package had been added in Guix on 2020-05-05, i.e., post Python 2 EOL. I think it is a "mistake" and instead should live in the channel "guix-past", but at the time, this channel did not exist, if I remember correctly. Anyway, that's a discussion for bug#46132. Just to understand, does your suggestion is: should the author of 3142daccbe updating python-setuptools have done these 2 checks? (Maybe more for some cases.) In my mind, no. And having a separate file containing all the python2 variants ease the review of each and then janitor. 1: https://github.com/kozec/syncthing-gtk/issues/487 2: https://salsa.debian.org/debian/syncthing-gtk/-/tree/python3-port Cheers, simon