From: Gabriel Wicki <gabriel@erlikon.ch>
To: help-guix@gnu.org
Subject: pyproject build (hatchling) with entry-points
Date: Mon, 2 Dec 2024 22:46:48 +0100 [thread overview]
Message-ID: <dw7rbbh2wrzkgf65zrmfujnfve3rfcpb33ox6tgwhwfdegtn7y@cln7jwhzinuc> (raw)
Hi there!
I have created a Python application that seems to build just fine (using
a pyproject.toml file and the hatchling build system, by invoking
`python3 -m build`), including script entrypoints and everything.
Unfortunately I am not as lucky with my Guix packaging attempts. My
Python project creates a wheel and a tar.gz dist file with the
corresponding entry_points.txt file, but the pyproject-build-system's
create-entrypoints phase does not seem to pick it up. Making the guix
build fail I see that no entry_points.txt makes its way into the build
process. Am I doing it wrongly? Am I missing something? Is this a
known issue?
Thanks for any and all pointers leading me further down the path
gabber
next reply other threads:[~2024-12-02 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 21:46 Gabriel Wicki [this message]
2024-12-02 23:05 ` pyproject build (hatchling) with entry-points aurtzy
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=dw7rbbh2wrzkgf65zrmfujnfve3rfcpb33ox6tgwhwfdegtn7y@cln7jwhzinuc \
--to=gabriel@erlikon.ch \
--cc=help-guix@gnu.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.
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).