pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2022-08-02	py-validate-pyproject: updated to 0.9	adam	3	-7/+8
	Version 0.9 - Use ``tomllib`` from the standard library in Python 3.11+ Version 0.8.1 - Workaround typecheck inconsistencies between different Python versions - Publish :pep:`561` type hints Version 0.8 - New :pypi:`pre-commit` hook - Allow multiple TOML files to be validated at once via CLI (no changes regarding the Python API).
2022-04-13	py-validate-pyproject: updated to 0.7.2	adam	2	-6/+6
	Version 0.7.2 - ``setuptools`` plugin: - Allow ``dependencies``/``optional-dependencies`` to use file directives
2022-04-13	py-validate-pyproject: add missing build dependency on py-setuptools_scm	wiz	1	-1/+2

2022-04-05	py-validate-pyproject: added version 0.7.1	adam	5	-0/+157
	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.