GNU bug report logs - #69997
Should ‘guix import pypi’ get dependencies from pyproject files?

Previous Next

Full log

View this message in rfc822 format

From: Lars-Dominik Braun <lars <at> 6xq.net>
To: Ludovic Courtès <ludovic.courtes <at> inria.fr>
Cc: Tanguy LE CARROUR <tanguy <at> bioneland.org>, 69997 <at> debbugs.gnu.org, Sharlatan Hellseher <sharlatanus <at> gmail.com>
Subject: bug#69997: Should ‘guix import pypi’ get dependencies from pyproject files?
Date: Sun, 15 Dec 2024 17:12:12 +0100

[Message part 1 (text/plain, inline)]

Hi,

> Should ‘guix import pypi’ attempt to get dependency information from
> ‘pyproject.toml’, in addition to ‘requirements.txt’ and wheel ‘METADATA’
> as it already does?

attached patches allow parsing the standardized pyproject.toml fields
for dependencies. This won’t work for poetry (we need a different
version parser for that), but it’s a start.

Lars

[0001-import-pypi-Support-extracting-dependencies-from-pyp.patch (text/plain, attachment)]

[0002-import-pypi-Add-python-wheel-to-native-inputs-if-set.patch (text/plain, attachment)]

[0003-import-pypi-Default-to-setuptools-as-build-system-in.patch (text/plain, attachment)]

[0004-import-pypi-Move-deduplication-to-final-processing-s.patch (text/plain, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.