BSD Portstextproc/py-validate-pyproject 0.26 NetBSD
Validation library and CLI tool for checking on pyproject.toml files
- System
- NetBSD
- Repository
- pkgsrc
- Maintainer
- [email protected]
- Last update
- Commit
e521fc3a7d- License
- mpl-2.0 AND mit AND modified-bsd
- Categories
- textproc, python
- Package size
- 86.0 KiB, 411.7 KiB installed
Description
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.
In the other systems
| System | Port | Version |
|---|---|---|
| NetBSD | textproc/py-validate-pyproject | 0.26 |
| DragonFly | devel/py-validate-pyproject | 0.24 |
Install
Binary package:
pkgin install py311-validate-pyprojectFrom pkgsrc:
cd /usr/pkgsrc/textproc/py-validate-pyproject && make install cleanPackages
The version each package repository carries. “-” means the repository builds no package of it, “n/a” that there is no such repository.
| Repository | Version |
|---|---|
| NetBSD 10.1 x86_64 | 0.26 |
| NetBSD 10.1 aarch64 | 0.25 |
| SmartOS / illumos x86_64 | 0.26 |
| macOS 15 arm64 | 0.26 |
Dependencies
Run dependencies 2
No port depends on this one.
Configuration
No options to configure.
- Service scripts
- none
- Flavors
py312-validate-pyproject-0.26,py313-validate-pyproject-0.26,py314-validate-pyproject-0.26