Up to [cvs.NetBSD.org] / pkgsrc / textproc / py-validate-pyproject
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
py-validate-pyproject: updated to 0.26 0.26 * Add support for :pep:`808` partially dynamic metadata by :user:`henryiii` (:pr:`314`) * Allow multiple schemas describing the same tool when the schema definitions are identical by :user:`henryiii` (:pr:`303`) * Improve ``SchemaStore`` compatibility by supporting relative schema URLs by :user:`henryiii` (:pr:`306`) * Apply filtering before loading ``validate_pyproject.multi_schema`` entry points by :user:`henryiii` (:pr:`318`) * Add timeouts to network requests to avoid indefinite blocking by :user:`henryiii` (:pr:`319`)
py-validate-pyproject: updated to 0.24.1 Version 0.24.1 * Fixed multi plugin id was read from the wrong place * Implemented alternative plugin sorting
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``
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
py-validate-pyproject: updated to 0.16 Version 0.16 - Fix setuptools ``readme`` field - Fix ``oneOf <> anyOf`` in setuptools schema - Add previously omitted type keywords for string values - Add schema validator check - Add ``SchemaStore`` conversion script - Allow tool(s) to be specified via URL (added CLI option: ``--tool``) - Support ``uint`` formats (as used by Ruff's schema) - Allow schemas to be loaded from ``SchemaStore`` (added CLI option: ``--store``)
python/wheel.mk: simplify a lot, and switch to 'installer' for installation This follows the recommended bootstrap method (flit_core, build, installer). However, installer installs different files than pip, so update PLISTs for all packages using wheel.mk and bump their PKGREVISIONs.
py-validate-pyproject: updated to 0.14 Version 0.14 - Ensure reporting show more detailed error messages for ``RedefiningStaticFieldAsDynamic`` - Add support for ``repo-review``
py-validate-pyproject: updated to 0.12.2
Version 0.12.2
- ``setuptools`` plugin:
- Fix problem with ``license-files`` patterns,
by removing ``default`` value.
Version 0.12.1
- ``setuptools`` plugin:
- Allow PEP 561 stub names in ``tool.setuptools.package-dir``,
Version 0.12
- ``setuptools`` plugin:
- Allow PEP 561 stub names in ``tool.setuptools.packages``,
Version 0.11
- Improve error message for invalid replacements in the ``pre_compile`` CLI,
- Allow package to be build from git archive,
- Improve error message for invalid replacements in the ``pre_compile`` CLI,
- Error-out when extra keys are added to ``project.authors/maintainers``,
- De-vendor ``fastjsonschema``,
Version 0.10.1
- Ensure ``LICENSE.txt`` is added to wheel.
Version 0.10
- Add ``NOTICE.txt`` to ``license_files``,
- Use default SSL context when downloading classifiers from PyPI,
- Remove ``setup.py``,
- Explicitly limit oldest supported Python version
- Replace usage of ``cgi.parse_header`` with ``email.message.Message``
py-validate-pyproject: updated to 0.9 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*).
py-validate-pyproject: added version 0.7.1 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.