GNU bug report logs - #46848
[PATCHES] [core-updates] PEP 517 python-build-system

Previous Next

Full log

Message #26 received at 46848 <at> debbugs.gnu.org (full text, mbox):

From: Lars-Dominik Braun <lars <at> 6xq.net>
To: Hartmut Goebel <h.goebel <at> crazy-compilers.com>
Cc: guix-devel <at> gnu.org, 46848 <at> debbugs.gnu.org
Subject: Re: Questions regarding Python packaging
Date: Tue, 6 Jul 2021 14:16:03 +0200

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

Hi again,

> No, try
> 
> 	git clone https://github.com/pypa/pep517.git
> 	cd pep517
> 	pip wheel --use-pep517 -v .
> 
> which has no setup.py and uses flit instead. pip can build it, because
> it supports PEP 517-based builds. As I said, if we decide to keep it
> bundled with our python package, there’s no good reason to choose
> pypa-build.
I now have a proof of concept for a pip-based python-build-system, see
1st patch. The changeset is quite small, but it does not handle testing
at all right now.

Note that alot of setuptools-based packages lack a dependency on
python-wheel (2nd patch; pardon the whitespace errors), which is
required when using pyproject.toml (and also declared there, but our
Python importer cannot read that file yet). But – as expected – that’s
really the only issue I’ve encountered while rebuilding alot of Python
packages so far.

Cheers,
Lars

[0001-dirty-build-Build-Python-packages-using-pip.patch (text/x-diff, attachment)]

[0002-dirty-Fix-build-errors.patch (text/x-diff, attachment)]

Previous Next

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