Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #12625

Re: PEP-517/PEP-518 Support In Debian

Path csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From Scott Kitterman <debian@kitterman.com>
Newsgroups linux.debian.maint.python
Subject Re: PEP-517/PEP-518 Support In Debian
Date Fri, 05 Jun 2020 02:00:01 +0200
Message-ID <Ae7W9-4r8-9@gated-at.bofh.it> (permalink)
References <zUTqG-72H-9@gated-at.bofh.it> <zV64x-6yd-3@gated-at.bofh.it> <Ae7Mt-4nS-1@gated-at.bofh.it>
X-Original-To debian-python@lists.debian.org
X-Mailbox-Line From debian-python-request@lists.debian.org Thu Jun 4 23:58:01 2020
Old-Return-Path <debian@kitterman.com>
X-Amavis-Spam-Status No, score=-12.18 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02, PGPSIGNATURE=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate: -5.5
Dkim-Signature v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1591315066; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-type : from; bh=OlY7R0dRLwuIm/Y8a1JMM6WaPgPF6abNL51OQaIOj9s=; b=H0QS0+plByhlXaFrfWkbP2BDaKMf+Jz2iTzKhpogmyO51MvHvj8ZC+QN3XiJnnYUFtIzc stldSjLrMASnJA8AQ==
Dkim-Signature v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1591315066; h=from : to : subject : date : message-id : in-reply-to : references : mime-version : content-type : from; bh=OlY7R0dRLwuIm/Y8a1JMM6WaPgPF6abNL51OQaIOj9s=; b=oWjmztvuW9r6E4OhBvS37IzFVWYi0Vz1OIf/V9eftCiaxTo5zmx7xRJposNrwCfUL+c0A VItHeM2KXHMsYoCN9o84qzxz/d0nmRyE7uOj+amEtsLvbxxsa8Fo22n3aAIwdfpEWFQgsrX Bac4eBuQHfByrhdcpD2e6XHAEIW1WKv7VXi2dl3SqZ7hfE04Rf6gAaGwHdSbstFME+BHAd1 7CS1wVQG0BYqz2Ef2/Ku5hShBplvrEchBXATciA6+94NGvuavPLwIul9vcTuuuMn25Qr8PZ Gp9NNXja8ORugz8WzuVZ/XUD/1fp1+w+WIp6EzIXj+7oCFLTbGG05McFcsDw==
MIME-Version 1.0
Content-Type multipart/signed; boundary="nextPart9668416.4blRGyc2pk"; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Mailing-List <debian-python@lists.debian.org> archive/latest/18331
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/2906900.Ui2l7W3ZyW@sk-desktop
Approved robomod@news.nic.it
Lines 105
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Thu, 04 Jun 2020 19:57:46 -0400
X-Original-Message-ID <2906900.Ui2l7W3ZyW@sk-desktop>
X-Original-References <1901857.gxORzZljd2@sk-desktop> <3852987.UMqJ38MGZC@sk-desktop> <87v9k6s8mo.fsf@DigitalMercury.dynalias.net>
Xref csiph.com linux.debian.maint.python:12625

Show key headers only | View raw


[Multipart message — attachments visible in raw view] - view raw

On Thursday, June 4, 2020 7:39:59 PM EDT Nicholas D Steeves wrote:
> Hi,
> 
> Scott Kitterman <debian@kitterman.com> writes:
> > On Monday, April 13, 2020 5:18:53 AM EDT Dmitry Shachnev wrote:
> >> Hi Scott!
> >> 
> >> On Sun, Apr 12, 2020 at 06:31:57PM -0400, Scott Kitterman wrote:
> >> > This being roughly the mid-point in the development cycle, I thought it
> >> > might be good to see where we are in terms of future Python packaging
> >> > developments.
> >> > 
> >> > As I understand it, PEP-517 and PEP-518 are 'the future'.
> 
> While importing the latest release of Fissix (a grammar parser used by
> Bowler) I found that it had a pyproject.toml but no setup.py.
> 
> >> > I took a look at the presence of pyproject.toml files in the Debian
> >> > archive. There are currently 99 packages.  Of those, only 28 specify a
> >> > 'build-backend', which is required by 517/518 to be useful for building
> >> > a
> >> > package.
> >> > 
> >> > 25 specify: build-backend = "setuptools.build_meta" (including
> >> > setuptools)
> >> > 3 specify: build-backend = "flit_core.buildapi" (including flit)
> >> 
> >> pyqt5 and pyqt5webengine specify: build-backend = "sipbuild.api".
> 
> Is there existing documentation around if/how build-backend can be used
> to work around the absence of setup.py?
> 
> > So they do.  They didn't show up in my codesearch.d.n results, that makes
> > me wonder what else I missed.  If anyone has an idea of a better way to
> > track this, please speak up.
> > 
> >> > If build-backend is not specified, the build system has to fall back to
> >> > setup.py.
> >> > 
> >> > I've recently package flit (just arrived in Testing) and written a flit
> >> > plugin for pybuild that's pending review for merging[1].  I also
> >> > packaged
> >> > pep517 for our pip package, so that's available to support future
> >> > Debian
> >> > tool development in this area.
> > 
> > P1otr merged the flit plugin a little while ago, so it'll be in the next
> > dh- python upload.
> 
> I think this is probably what is needed to unblock work on fissix (and
> thus Bowler), because its Makefile has:
> 
>     python -m pip install -r requirements.txt
>     python -m pip install -r requirements-dev.txt
>     python -m flit install --symlink
> 
> [snip]
> 
> Any advise for existing workarounds would be appreciated.  So far the
> only idea I've had is writing or generating a setup.py, and then adding
> it as a quilt patch.

That is probably the best approach for now.

Ultimately we have two choices:

1.  Add per-backend capability into pybuild as I have done with flit.  
Depending on how many of them there are, this may or may not be a reasonable 
approach.

2.  Use the pep517 module with pip in our package build system.  I think 
Fedora has gone this direction.

I prefer #1 because we want to produce a traditional bdist, not wheels, but 
we'll have to do the work.  I don't think we want an impenetrable morass of 
zip files in /usr/lib/python3/dist-packages.

Scott K 

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

PEP-517/PEP-518 Support In Debian Scott Kitterman <debian@kitterman.com> - 2020-04-13 00:40 +0200
  Re: PEP-517/PEP-518 Support In Debian Paul Wise <pabs@debian.org> - 2020-04-13 05:50 +0200
    Re: PEP-517/PEP-518 Support In Debian Scott Kitterman <debian@kitterman.com> - 2020-04-13 06:00 +0200
  Re: PEP-517/PEP-518 Support In Debian Dmitry Shachnev <mitya57@debian.org> - 2020-04-13 11:20 +0200
    Re: PEP-517/PEP-518 Support In Debian Scott Kitterman <debian@kitterman.com> - 2020-04-13 14:10 +0200
      Re: PEP-517/PEP-518 Support In Debian Nicholas D Steeves <nsteeves@gmail.com> - 2020-06-05 01:50 +0200
        Re: PEP-517/PEP-518 Support In Debian Scott Kitterman <debian@kitterman.com> - 2020-06-05 02:00 +0200
          Re: PEP-517/PEP-518 Support In Debian Nicholas D Steeves <nsteeves@gmail.com> - 2020-06-05 02:50 +0200

csiph-web