From: Lars-Dominik Braun <lars@6xq.net>
To: Ian Eure <ian@retrospec.tv>
Cc: jgart <jgart@dismail.de>, "Ludovic Courtès" <ludo@gnu.org>,
"Sharlatan Hellseher" <sharlatanus@gmail.com>,
74715@debbugs.gnu.org, me@bonfacemunyoki.com, marius@gnu.org,
guix-devel@gnu.org, tanguy@bioneland.org
Subject: Re: bug#74715: Request for merging "python-team" branch
Date: Sun, 15 Dec 2024 07:28:49 +0100 [thread overview]
Message-ID: <Z153IS4JWlm0Y_gi@noor.fritz.box> (raw)
In-Reply-To: <382af619-0dcd-4b4e-9e26-3576766c7aca@app.fastmail.com>
Hi Ian,
> Since this merge landed, the builds for several Python packages in my personal channel broke. Any package using pyproject-build-system for a Python project using setuptools seems to be affected.
as Sharlatan Hellseher wrote in https://issues.guix.gnu.org/issue/74715#4,
you need to add python-setuptools and python-wheel to your
setuptools-based packages. The default python toolchain used by
pyproject-build-system (python-sans-pip-wrapper from
gnu/packages/python.scm) does not include these packages any more,
since they are technically not required and declaring them as *real*
inputs allows using different versions of these packages more easily
for packages, which require them. Plus there are quite a few packages,
which build using different build systems nowadays.
The python importer should probably be updated to read pyproject.toml
and parse the [build-system] table (there is a toml parser in Guix now,
so this should be easy).
Lars
prev parent reply other threads:[~2024-12-15 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bjxo8phy.fsf@gmail.com>
2024-12-10 19:31 ` Request for merging "python-team" branch Sharlatan Hellseher
2024-12-13 15:55 ` bug#74715: " Ludovic Courtès
2024-12-13 17:00 ` jgart
2024-12-15 1:00 ` Ian Eure
2024-12-15 6:24 ` Kaelyn via Development of GNU Guix and the GNU System distribution.
2024-12-15 6:28 ` Lars-Dominik Braun [this message]
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=Z153IS4JWlm0Y_gi@noor.fritz.box \
--to=lars@6xq.net \
--cc=74715@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
--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).