From: Lars-Dominik Braun <lars@6xq.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Tanguy Le Carrour <tanguy@bioneland.org>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
jgart <jgart@dismail.de>, Marius Bakke <marius@gnu.org>,
Sharlatan Hellseher <sharlatanus@gmail.com>,
69997@debbugs.gnu.org
Subject: bug#69997: Should ‘guix import pypi’ get dependencies from pyproject files?
Date: Wed, 27 Mar 2024 07:49:27 +0100 [thread overview]
Message-ID: <ZgPBd4TjMRz8q6lq@noor.fritz.box> (raw)
In-Reply-To: <877chqtvsk.fsf@inria.fr>
Hey Ludo,
> Should ‘guix import pypi’ attempt to get dependency information from
> ‘pyproject.toml’, in addition to ‘requirements.txt’ and wheel ‘METADATA’
> as it already does?
yes it should. It’s the next logical step after having a
pyproject-build-system. The python-team branch (not sure whether Ricardo
had time to merge it yet) adds a TOML parser to Guix as a first step.
> It might be more complicated than we’d like: in some cases, that file
> seems to be used as a “trampoline” to Poetry. For instance, in
> python-pypugjs, the ‘requires’ bit delegates everything to Poetry:
The file is always a trampoline to other build systems, like setuptools
or poetry. That’s (unfortunately) by design, see the [build-system]
section.
> [tool.poetry.dependencies]
> python = "^3.8"
> Jinja2 = "^3.1.1"
> Mako = "^1.1.3"
> tornado = "^6.0.4"
> six = "^1.15.0"
> coverage = "^6.3.2"
> nose = "^1.3.7"
> Flask = "^2.1.1"
> charset-normalizer = "^2.1.0"
> flake8 = "^4.0.1"
That’s unfortunate, because the
specification includes a common field for dependencies:
https://packaging.python.org/en/latest/specifications/pyproject-toml/#dependencies-optional-dependencies
I guess we’ll have to deal with these idiosyncracies as well :(
Lars
prev parent reply other threads:[~2024-03-27 6:50 UTC|newest]
Thread overview: 11+ 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 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZgPBd4TjMRz8q6lq@noor.fritz.box \
--to=lars@6xq.net \
--cc=69997@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=ludovic.courtes@inria.fr \
--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 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.