Bug#1028188: ITP: python-validate-pyproject -- Automated checks on pyproject.toml by JSON Schema definitions
Package: wnpp
Severity: wishlist
Owner: Carsten Schoenert <c.schoenert@t-online.de>
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name : python-validate-pyproject
Version : 0.10.1
Upstream Contact: Anderson Bravalheri <andersonbravalheri@gmail.com>
* URL : https://github.com/abravalheri/validate-pyproject
* License : BSD, MIT, MPL-2.0
Programming Lang: Python
Description : Automated checks on pyproject.toml by JSON Schema definitions
With the approval of PEP 517 and PEP 518, the Python community shifted
towards a strong focus on standardisation for packaging software, which
allows more freedom when choosing tools during development and make sure
packages created using different technologies can interoperate without the
need for custom installation procedures.
.
This shift became even more clear when PEP 621 was also approved, as a
standardised way of specifying project metadata and dependencies.
.
validate-pyproject was born in this context, with the mission of validating
pyproject.toml files, and make sure they are compliant with the standards
and PEPs. Behind the scenes, validate-pyproject relies on JSON Schema files,
which, in turn, are also a standardised way of checking if a given data
structure complies with a certain specification.
This package is a dependency for pdm-backend (not yet filed a ITP) and
will be maintained within the Debian Python team.
Upstream uses a vendored version of fastjsonschema shipped in the folder
src/validate_pyproject/_vendor/. The reasoning isn't currently clear why
this is needed. Due this vendoring there are multiple licenses comes to
play.
I've tried to entagle this vendoring but hadn't luck until yet.
pdm-backend calles itself it is the successor for pdm-pep517 but hasn't
reached a stable version number yet.
Reply to: