Hi, zimoun <[email protected]> writes:
> HI Maxim, > > Thanks for your answer. > [...] > 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? I wouldn't revert; Python 2 should not hold anyone from keeping packages up to date. > 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. My opinion is that moving packages about to be removed is not worth the hassle. Most Python 2 packages are already in a single module: the gigantic python-xyz.scm ;-) >> 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.) I just committed a series of python2-* package removal, along with using this port for our syncthing-gtk package. It now builds, at least! See commit de8dc9039b. > 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. Fair enough. Removed in 23a5dcce1d. Thanks! Maxim
