Ubuntu
python-validate-pyproject package

python-validate-pyproject 0.16-1 source package in Ubuntu

Changelog

python-validate-pyproject (0.16-1) unstable; urgency=medium

  * [62f2eb4] New upstream version 0.16
  * [9121f42a] Rebuild patch queue from patch-queue branch
    Just refresh the existing patches.
  * [342b7f8] d/rules: Extend dh_clean to clean up .mypy_cache folder
  * [7d399b1] d/rules: Add some tests to exclude
  * [09debec] autopkgtest: Exclude same tests here too
  * [28d0d11] d/copyright: Update year data

 -- Carsten Schoenert <email address hidden>  Sat, 27 Jan 2024 19:01:35 +0100

Upload details

Uploaded by:
Debian Python Team
Uploaded to:
Sid
Original maintainer:
Debian Python Team
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Noble release universe misc

Builds

Noble: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-validate-pyproject_0.16-1.dsc 2.7 KiB 5caf8f98f32748ad0977b8821fde1323fa3c1f4120fceebc7978d8cbca663cd0
python-validate-pyproject_0.16.orig.tar.gz 90.6 KiB 013f36f6bfe3f4f31a5d2b1f4e97a3abf2896974364a4379077a89ac44a818f9
python-validate-pyproject_0.16-1.debian.tar.xz 8.0 KiB 2b6e11bc67032a372d8eb87f90e3a10ca7f89229e7bc039c60b473dbaee3800e

Available diffs

No changes file available.

Binary packages built by this source

python-validate-pyproject-doc: Automated checks on pyproject.toml by JSON Schema definitions (Documentation)

 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 contains the Sphinx based HTML documentation.

python3-validate-pyproject: 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 contains the module for Python 3.