Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Nicholas D Steeves <nsteeves@gmail.com>
Newsgroups: linux.debian.maint.python
Subject: Re: PEP-517/PEP-518 Support In Debian
Date: Fri, 05 Jun 2020 01:50:01 +0200
Message-ID: <Ae7Mt-4nS-1@gated-at.bofh.it>
References: <zUTqG-72H-9@gated-at.bofh.it> <zV3q1-4Sl-5@gated-at.bofh.it> <zV64x-6yd-3@gated-at.bofh.it>
Old-Return-Path: <nsteeves@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Approved: robomod@news.nic.it
Lines: 95
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:12624

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

Scott Kitterman <debian@kitterman.com> writes:

> On Monday, April 13, 2020 5:18:53 AM EDT Dmitry Shachnev wrote:
>> Hi Scott!
>>=20
>> 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.
>> >=20
>> > 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 buildin=
g a
>> > package.
>> >=20
>> > 25 specify: build-backend =3D "setuptools.build_meta" (including setup=
tools)
>> > 3 specify: build-backend =3D "flit_core.buildapi" (including flit)
>>=20
>> pyqt5 and pyqt5webengine specify: build-backend =3D "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=20
> wonder what else I missed.  If anyone has an idea of a better way to trac=
k=20
> this, please speak up.
>
>> > If build-backend is not specified, the build system has to fall back to
>> > setup.py.
>> >=20
>> > 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 packa=
ged
>> > pep517 for our pip package, so that's available to support future Debi=
an
>> > 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.

Thanks,
Nicholas

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE4qYmHjkArtfNxmcIWogwR199EGEFAl7Zhk8ACgkQWogwR199
EGHhRRAAo+5R6CRnVUXC2riTbk++lIAW+UnTOhYdIVJZGrWc9SVrOw+X8EvK1//e
HuHfnSETACydvKd3LqXuDhuP1VsZzWWpxJisS5ZI00B/BX0oYdDzvHAmiPmCOO+O
CxR+VLsO9MzHP9bXvHdNJiuCMA5CLaNIQKtC6yt2cxIVE44l8KwNi5U9kiojuZZV
q71RvBoE+HizIN3glgTQWzVIQCBYf3+fYTVm7iQ73EAzZaGjkRYw0SJY1bYE+MqL
f170ytDsrbcuRKfZntNsM2I9VbSVKuYfuuktNRVUYlUEayfZsoNjW/1Yt+F793o1
wixQGdjyR18bDG+AEk5iozpz+FnJIooIdTzLcVehxH4hoa6nLLJX/lAMp8ZOYU17
UWZP8mekUbqtuJFubW7fZRnZlPNOHP1MJO2cOXl+xzOiiRmZjeuwHgt7dKiAfYNe
aao4gHvHocB1V2ssLIiEHDpzClhRTaULHt5nxWQRx69rfAgHq1WEP3HQyZYYk/J5
vL1N0en6GrBtMep5MrY7wCCNimz4GQWZ0DWq97Vc7deVAy1Jw8tRYLphDmcXQ5Kp
hb2V0HL0qWzMqm5y4P88bUapyKBBKQ1ZFio4ev4ezhqCoKcQ8+KzUig7ee4h8g01
Qr6LNpNXU29bZEqAPS/NLqKcNPTByxj4mhrCjNbxKuDqN+xDXAg=
=FhN/
-----END PGP SIGNATURE-----
--=-=-=--