From: Andreas Enge <andreas@enge.fr>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: guix-devel@gnu.org
Subject: Re: Python
Date: Sat, 25 Feb 2023 19:00:30 +0100 [thread overview]
Message-ID: <Y/pMvuWMVv5btFyj@jurong> (raw)
In-Reply-To: <Y/o921Gu+kwt07N7@noor.fritz.box>
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
next prev parent reply other threads:[~2023-02-25 18:01 UTC|newest]
Thread overview: 128+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 9:05 Merging core-updates? Julien Lepiller
2023-02-12 11:06 ` Andreas Enge
2023-02-12 11:52 ` Julien Lepiller
2023-02-12 11:58 ` Julien Lepiller
2023-02-12 13:05 ` Christopher Baines
2023-02-20 11:10 ` Christopher Baines
2023-02-12 17:08 ` Andreas Enge
2023-02-12 18:29 ` Kaelyn
2023-02-13 20:04 ` Efraim Flashner
2023-02-13 21:36 ` Kaelyn
2023-02-14 14:50 ` Efraim Flashner
2023-02-14 20:29 ` Kaelyn
2023-02-15 0:07 ` Kaelyn
2023-02-12 18:40 ` Janneke Nieuwenhuizen
2023-02-13 11:34 ` Janneke Nieuwenhuizen
2023-02-13 13:57 ` Andreas Enge
2023-02-15 8:39 ` Janneke Nieuwenhuizen
2023-02-16 14:19 ` Andreas Enge
2023-02-16 15:03 ` bug#49985: " Janneke Nieuwenhuizen
2023-02-16 15:24 ` Andreas Enge
2023-02-16 15:33 ` Julien Lepiller
2023-02-12 14:49 ` Josselin Poiret
2023-02-13 3:05 ` John Kehayias
2023-02-12 12:02 ` Leo Famulari
2023-02-21 23:01 ` Ludovic Courtès
2023-02-12 13:28 ` Christopher Baines
2023-03-05 19:52 ` Christopher Baines
2023-03-05 22:18 ` Merging core-updates? OFF TOPIC PRAISE Joshua Branson
2023-02-12 15:51 ` Merging core-updates? Efraim Flashner
2023-02-13 16:40 ` Katherine Cox-Buday
2023-02-13 17:11 ` John Kehayias
2023-02-13 20:22 ` Andreas Enge
2023-02-13 20:38 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-02-13 9:43 ` zimoun
2023-02-13 10:56 ` Architecture support [was: Re: Merging core-updates?] Efraim Flashner
2023-02-13 12:59 ` Architecture support Andreas Enge
2023-02-14 16:30 ` Architecture support [was: Re: Merging core-updates?] Andreas Enge
2023-02-14 16:40 ` Julien Lepiller
2023-02-15 9:45 ` Architecture support Andreas Enge
2023-02-17 16:49 ` Architecture support [was: Re: Merging core-updates?] Christopher Baines
2023-02-19 22:50 ` Architecture support Andreas Enge
2023-02-20 9:23 ` Christopher Baines
2023-02-14 20:10 ` Architecture support [was: Re: Merging core-updates?] Efraim Flashner
2023-02-15 9:35 ` Andreas Enge
2023-02-13 20:35 ` Merging core-updates? Andreas Enge
2023-02-13 21:31 ` Efraim Flashner
2023-02-14 18:27 ` Andreas Enge
2023-02-15 18:51 ` Andreas Enge
2023-02-15 19:19 ` Openjdk (was: Merging core-updates?) Andreas Enge
2023-02-16 11:03 ` Efraim Flashner
2023-02-16 11:38 ` Julien Lepiller
2023-02-18 11:28 ` Andreas Enge
2023-02-17 10:36 ` Andreas Enge
2023-02-17 14:49 ` Andreas Enge
2023-02-17 16:28 ` Andreas Enge
2023-02-17 17:27 ` Kaelyn
2023-02-18 10:55 ` Andreas Enge
2023-02-16 11:41 ` Merging core-updates? Maxime Devos
2023-02-16 16:03 ` Andreas Enge
2023-02-18 11:03 ` Ocaml (was: Merging core-updates?) Andreas Enge
2023-02-18 11:38 ` Andreas Enge
2023-02-19 9:15 ` Julien Lepiller
2023-02-20 10:35 ` Simon Tournier
2023-02-20 11:16 ` Julien Lepiller
2023-02-20 11:55 ` Ocaml Andreas Enge
2023-02-19 11:02 ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 11:15 ` Andreas Enge
2023-02-19 11:19 ` Andreas Enge
2023-02-19 15:10 ` Attila Lendvai
2023-02-21 16:24 ` Python Andreas Enge
2023-02-19 11:30 ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 20:31 ` Python Andreas Enge
2023-02-21 16:41 ` Python Andreas Enge
2023-02-22 14:23 ` Python Andreas Enge
2023-02-23 15:16 ` Python Andreas Enge
2023-02-24 16:47 ` Python Andreas Enge
2023-02-24 16:51 ` Python Andreas Enge
2023-02-24 18:08 ` Python Lars-Dominik Braun
2023-02-25 15:15 ` Python Andreas Enge
2023-02-25 15:45 ` Python Lars-Dominik Braun
2023-02-25 16:39 ` Python Andreas Enge
2023-02-25 16:56 ` Python Lars-Dominik Braun
2023-02-25 18:00 ` Andreas Enge [this message]
2023-02-25 18:06 ` Python Andreas Enge
2023-02-25 18:15 ` Python Andreas Enge
2023-02-25 18:33 ` Python Andreas Enge
2023-02-27 19:14 ` Python Lars-Dominik Braun
2023-02-28 15:05 ` Python Andreas Enge
2023-02-25 18:29 ` Python Andreas Enge
2023-03-11 11:20 ` Python Andreas Enge
2023-03-11 11:44 ` Python Andreas Enge
2023-03-15 13:49 ` Python Andreas Enge
2023-03-18 8:59 ` Python Lars-Dominik Braun
2023-03-18 9:15 ` Python Andreas Enge
2023-03-18 10:02 ` Python Lars-Dominik Braun
2023-03-18 10:13 ` Python Andreas Enge
2023-03-18 9:43 ` Python Lars-Dominik Braun
2023-03-18 19:37 ` Python Andreas Enge
2023-03-21 18:56 ` Python Lars-Dominik Braun
2023-03-30 9:57 ` Python Lars-Dominik Braun
2023-03-30 10:10 ` Python Andreas Enge
2023-04-03 17:29 ` PyQt in core-updates Andreas Enge
2023-04-04 7:55 ` Lars-Dominik Braun
2023-04-17 8:32 ` Andreas Enge
2023-03-30 11:05 ` Python Lars-Dominik Braun
2023-03-31 8:52 ` Python Andreas Enge
2023-02-27 18:55 ` Python Efraim Flashner
2023-02-27 19:12 ` Python Lars-Dominik Braun
2023-02-21 16:50 ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 11:47 ` Lars-Dominik Braun
2023-02-19 11:57 ` Andreas Enge
2023-02-19 15:50 ` Lars-Dominik Braun
2023-02-19 20:27 ` Python Andreas Enge
2023-02-25 17:44 ` Python Andreas Enge
2023-02-19 21:35 ` Python (was: Merging core-updates?) Andreas Enge
2023-02-19 22:08 ` Andreas Enge
2023-02-19 22:59 ` Kaelyn
2023-02-21 16:18 ` Andreas Enge
2023-02-19 19:55 ` Andreas Enge
2023-02-19 11:48 ` Andreas Enge
2023-02-19 22:24 ` Andreas Enge
2023-02-21 16:58 ` Andreas Enge
2023-02-22 9:40 ` Icecat (was: Python) Andreas Enge
2023-02-16 20:11 ` Merging core-updates? Josselin Poiret
-- strict thread matches above, loose matches on Subject: below --
2013-09-13 15:46 Python Andreas Enge
2013-09-13 16:25 ` Python Cyril Roelandt
2013-09-14 9:02 ` Python Andreas Enge
2013-09-13 21:32 ` Python Ludovic Courtès
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=Y/pMvuWMVv5btFyj@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=lars@6xq.net \
/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).