Ubuntu
python-validate-pyproject package

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

Changelog

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

  * [7320d1a] d/README.source: Update data about intersphinx extensions
  * [fc09971] New upstream version 0.18
  * [c2a6a84] Rebuild patch queue from patch-queue branch
    Updated patch:
    docs-Exclude-some-not-available-Sphinx-extensions.patch
  * [8602b7c] d/rules: Don't run test_cache_open_url in tests
  * [d60bcfa] autopkgtests: Ignore here test_cache_open_url too

 -- Carsten Schoenert <email address hidden>  Wed, 12 Jun 2024 18:21:28 +0200

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
Oracular release universe misc

Builds

Oracular: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
python-validate-pyproject_0.18-1.dsc 2.8 KiB de55d0bcd1f65c74b44aa40884092277780a9981134d258154ba211220ef8d99
python-validate-pyproject_0.18.orig.tar.gz 95.3 KiB 5112faea30595a5a014a3eff74aeae0ed95deb56e115c2f8bfc078652157f060
python-validate-pyproject_0.18-1.debian.tar.xz 8.2 KiB 801235b64a7972fa5860864e6290816d6280a2c20acc6bd3bc5b26e7e83f4238

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.