On April 13, 2020 3:44:31 AM UTC, Paul Wise <p...@debian.org> wrote:
>On Sun, Apr 12, 2020 at 10:32 PM Scott Kitterman wrote:
>
>> 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.
>
>Is there a tool that can report problems in pyproject.toml files?
>Either way I think that lintian needs to detect this particular issue.
Not that I know of, but I don't think it's time yet.
They're non-build uses for pyproject.toml, so if build-backend isn't present,
it just means that it isn't used for build reasons.
The pep517 package (python3-pep517) can validate metadata generated based on
pyproject.toml, but it spins up it's own environment using pip and does a
package sdist build to do so. I don't think that's what you have in mind.
In the pybuild plugin I did for flit, I do check for the correct build-backend
when autodetecting if the plugin should be used. Using python3-toml it's a one
liner. If we really want to head down rlthe path of checking, it ought to be
simple enough to write.
Scott K
