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: Mon, 13 Apr 2020 06:00:01 +0200
Message-ID: <zUYql-1Cc-1@gated-at.bofh.it>
References: <zUTqG-72H-9@gated-at.bofh.it> <zUYgF-1yD-1@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 30
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:12470



On April 13, 2020 3:44:31 AM UTC, Paul Wise <pabs@debian=2Eorg> wrote:
>On Sun, Apr 12, 2020 at 10:32 PM Scott Kitterman wrote:
>
>> I took a look at the presence of pyproject=2Etoml files in the Debian
>archive=2E
>> There are currently 99 packages=2E  Of those, only 28 specify a
>'build-backend',
>> which is required by 517/518 to be useful for building a package=2E
>
>Is there a tool that can report problems in pyproject=2Etoml files?
>Either way I think that lintian needs to detect this particular issue=2E

Not that I know of, but I don't think it's time yet=2E

They're non-build uses for pyproject=2Etoml, so if build-backend isn't pre=
sent, it just means that it isn't used for build reasons=2E

The pep517 package (python3-pep517) can validate metadata generated based =
on pyproject=2Etoml, but it spins up it's own environment using pip and doe=
s a package sdist build to do so=2E  I don't think that's what you have in =
mind=2E

In the pybuild plugin I did for flit, I do check for the correct build-bac=
kend when autodetecting if the plugin should be used=2E  Using python3-toml=
 it's a one liner=2E  If we really want to head down rlthe path of checking=
, it ought to be simple enough to write=2E

Scott K