./textproc/py-validate-pyproject, Validation library and CLI tool for checking on pyproject.toml files

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: CURRENT, Version: 0.24, Package name: py312-validate-pyproject-0.24, Maintainer: pkgsrc-users

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.


Required to run:
[devel/py-setuptools] [lang/python310]

Required to build:
[devel/py-setuptools_scm] [devel/py-packaging]

Master sites:

Filesize: 112.954 KB

Version history: (Expand)

CVS history: (Expand)


   2025-03-14 16:27:19 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-validate-pyproject: updated to 0.24

Version 0.24

* Fix integration with ``SchemaStore`` by loading extra/side schemas.
* Add support for loading extra schemas.
* Fixed verify author dict is not empty.
* Added support for ``validate_pyproject.multi_schema`` plugins with extra schemas.
* ``validate-pyproject`` no longer communicates test dependencies via the ``tests``
  extra and documentation dependencies dependencies via the \ 
``docs/requirements.txt`` file.
  Instead :doc:`pypa:dependency-groups` have been adopted to support CI environments.

  As a result, ``uv``'s high level interface also works for developers. You can \ 
use the :pypi:`dependency-groups`
  package on PyPI if you need to convert to a classic requirements list.
   2024-11-12 10:58:50 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-validate-pyproject: updated to 0.23

0.23
Validate SPDX license expressions
   2024-11-11 08:29:31 by Thomas Klausner | Files touched by this commit (862) 
Log message:
py-*: remove unused tool dependency

py-setuptools includes the py-wheel functionality nowadays
   2024-10-24 22:31:43 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-validate-pyproject: updated to 0.22

0.22

Prevent injecting defaults and modifying input in-place
   2024-10-16 11:47:43 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-validate-pyproject: updated to 0.21

Version 0.21

* Added support PEP 735
* Added support PEP 639
* Renamed ``testing`` extra to ``test``
* General updates in CI setup

Version 0.20

- ``setuptools`` plugin:
   * Update ``setuptools.schema.json``
   2024-08-14 12:56:49 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-validate-pyproject: updated to 0.19

Version 0.19

- Relax requirements about module names to also allow dash characters
- Migrate metadata to ``pyproject.toml``
   2024-05-22 11:00:14 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-validate-pyproject: updated to 0.18

v0.18
Allow overwrite when schemas refer to the same tool
   2024-05-07 21:22:07 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-validate-pyproject: updated to 0.17

v0.17

Update version regex according to latest packaging version
Remove duplicate # ruff: noqa
Remove invalid top-of-the-file # type: ignore statement
Align tool.setuptools.dynamic.optional-dependencies with \ 
`project.optional-dependencies
Bump min Python version to 3.8