From: Lars-Dominik Braun <lars@6xq.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>,
"Sharlatan Hellseher" <sharlatanus@gmail.com>
Cc: 69997@debbugs.gnu.org, Tanguy LE CARROUR <tanguy@bioneland.org>
Subject: bug#69997: Should ‘guix import pypi’ get dependencies from pyproject files?
Date: Mon, 16 Dec 2024 19:42:29 +0100 [thread overview]
Message-ID: <Z2B0lbJJ0A6bQbfW@noor.fritz.box> (raw)
In-Reply-To: <CAO+9K5qH9Sd7Lek8SWrs4SVF=A6488tnZHbKO==6+YWakjhUZQ@mail.gmail.com> <871py8f1f3.fsf@inria.fr>
Hi,
> It looks like we still take info from ‘requirements.txt’; is
> ‘pyproject.toml’ insufficient?
correct. As a first quality of life improvement I would keep the other
information sources, but as we improve the importer further (by adding
poetry support for example), we need to fall back on them less often
I hope.
> Lars, do you have a commit access?
I have, but please go ahead and merge it into master. My available time
slots to work on Guix are quite limited, so merging my patches – even
though I have commit access – speeds things up.
Lars
next prev parent reply other threads:[~2024-12-16 20:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 11:06 bug#69997: Should ‘guix import pypi’ get dependencies from pyproject files? Ludovic Courtès
2024-03-25 19:28 ` Sharlatan Hellseher
2024-03-26 7:54 ` Tanguy LE CARROUR
2024-03-26 16:04 ` Ludovic Courtès
2024-03-26 16:55 ` Tanguy LE CARROUR
2024-03-26 17:14 ` Tanguy LE CARROUR
2024-03-28 18:09 ` Ludovic Courtès
2024-03-29 7:46 ` Tanguy LE CARROUR
2024-03-29 9:06 ` Ludovic Courtès
2024-03-29 10:11 ` Tanguy LE CARROUR
2024-03-27 6:49 ` Lars-Dominik Braun
2024-12-15 16:12 ` Lars-Dominik Braun
2024-12-16 9:00 ` Ludovic Courtès
2024-12-16 10:26 ` Sharlatan Hellseher
2024-12-16 18:42 ` Lars-Dominik Braun [this message]
2024-12-16 1:30 ` Sharlatan Hellseher
2024-12-16 19:29 ` bug#69997: Should âguix import pypiâ " Sharlatan Hellseher
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z2B0lbJJ0A6bQbfW@noor.fritz.box \
--to=lars@6xq.net \
--cc=69997@debbugs.gnu.org \
--cc=ludovic.courtes@inria.fr \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.