Am Sat, Feb 25, 2023 at 05:56:59PM +0100 schrieb Lars-Dominik Braun: > Well, there are reasons no-one is updating the Python ecosystem > regularly…
;-) > I don’t know for sure why any of these packages’ tests fail. typeguard > looks like it expects specific strings from Python or one of its libraries > – safe to ignore. So you suggest to add a #:test? #f? > sgmllib3k looks pretty dead upstream. Perhaps it’s > not even needed any more? Updates to Python packages (via `guix refresh`) > do not update dependencies and thus the list of inputs/native-inputs > are most likely outdated. Indeed, dead upstream. It has two dependents: quodlibet in the music module. There it is given as an input, but I do not see it in the pyproject.toml file, so it may indeed not be needed. It is also a propagated input of python-feedparser, which is an input to quodlibet and a (small) number of other packages: Building the following 6 packages would ensure 8 dependent packages are rebuilt: emacs-calibredb@2.12.0 limnoria@2019.11.22 rss2email@3.14 quodlibet@4.5.0 python-woob@3.0 gfeeds@1.0.3 We are at version 6.0.8 (from June 2021), but I also tried the latest release 6.0.10 (from May 2022). Even in its git repository, the pyproject.toml has this: [tool.poetry.dependencies] python = ">=3.7" sgmllib3k = "^1.0.0" And indeed, it does not build without. One option would be to disable the tests of sgmllib3k; then it would be nice if we could build any of the binaries depending on it to have a real test case. But they all seem to have lots of other dependencies (for instance python-cheetah for quodlibet, which also fails). Andreas