From: Lars-Dominik Braun <lars@6xq.net>
To: "Alice BRENON" <alice.brenon@ens-lyon.fr>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: tanguy@bioneland.org, me@bonfacemunyoki.com,
75400-done@debbugs.gnu.org, jgart@dismail.de, marius@gnu.org,
sharlatanus@gmail.com
Subject: [bug#75400] [PATCH] Fixing python-spacy
Date: Tue, 7 Jan 2025 15:18:32 +0100 [thread overview]
Message-ID: <Z303uB2pLF5MtNDb@noor.fritz.box> (raw)
In-Reply-To: <87h66c7zvr.fsf@gnu.org> <20250106124414.7861f9b8@ens-lyon.fr>
Hi Alice,
via:
> Cc’ing the Python team for feedback on your other comments:
>
> https://issues.guix.gnu.org/75400
> - the first issue is naturally the new required dependencies in `native-inputs`
> mentioned in bdde278dc9c565d8e9d11427c3a670ba86808af5 an visible in many
> python packages commit these past weeks. Surprisingly, I managed to compile
> `python-spacy` by adding only `python-wheel`, without `python-setuptools`.
> What makes both required? Are we sure that both were required in each and
> every python package recently modified?
in short: yes. I can’t tell for sure for this exact case because
the output of `guix graph` is too big for `xdot` to handle, but it’s
likely python-setuptools is implicitly propagated through some dependency
(perhaps a bug like https://issues.guix.gnu.org/25235) to python-spacy
and thus it looks like it’s “not required”.
Lars
next prev parent reply other threads:[~2025-01-07 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 11:44 [bug#75400] [PATCH] Fixing python-spacy Alice BRENON
2025-01-06 14:58 ` bug#75400: " Ludovic Courtès
2025-01-07 14:18 ` Lars-Dominik Braun [this message]
2025-01-07 14:27 ` [bug#75400] " Alice BRENON
2025-01-08 10:08 ` Ludovic Courtès
2025-01-08 15:30 ` jgart via Guix-patches via
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=Z303uB2pLF5MtNDb@noor.fritz.box \
--to=lars@6xq.net \
--cc=75400-done@debbugs.gnu.org \
--cc=alice.brenon@ens-lyon.fr \
--cc=jgart@dismail.de \
--cc=ludo@gnu.org \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.org \
/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).