vereqsyn
Bi-directional versions.cfg <–> requirements.txt synchronization
The name vereqsyn stands for version.cfg reqirements.txt synchronization.
This program can be used to synchronize a versions.cfg used by
zc.buildout with a requirements.txt
as used by pip.
This is be helpful to keep using zc.buildout but get version updates via
GitHub's Dependabot.
Table of Contents
Installation
pip install vereqsyn
Usage
vereqsyn --help
vereqsyn versions.cfg requirements.txt
Constraints
versions.cfgis the source of truth.requirements.txtcan get recreated.- So
versions.cfgcan contain comments, the ones inrequirements.txtare lost when running recreate.
Hacking
Run the tests
hatch run cov
Run the code formatter
To lint the code:
hatch fmt
To format the code:
hatch fmt -f
Cut a release
-
Update release date in
Changes.md. -
hatch build -
cd dist twine upload -r pypi rm vereqsyn-*
-
hatch version <new version number> -
Update
Changes.md: Enter new version as unreleased.
License
vereqsyn is distributed under the terms of the MIT license.
Metadata
Release files for vereqsyn 1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vereqsyn-1.1.tar.gz | 33.0 kB | Without provenance | Details for vereqsyn-1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| vereqsyn-1.1-py3-none-any.whl | Python 3 | none | any | Details for vereqsyn-1.1-py3-none-any.whl |
Total release size: 38.8 kB
Release files / vereqsyn-1.1.tar.gz
| Download URL | vereqsyn-1.1.tar.gz |
|---|---|
| Size | 33.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1d0a15a13bff8d1ef26078c151d5cfbe33b7f70f8789ee696724f889af8991b7
|
|
BLAKE2b-256 checksum How to use checksums |
50156c1a2a0bccf35cd79b2cb501d18d2e38049bff66b16c1fbc9a9c089ffeb8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / vereqsyn-1.1-py3-none-any.whl
| Download URL | vereqsyn-1.1-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad002a5a1cf9cf8ef5d5cc52cf05367be46b365973f22f683a5495a691ee4d35
|
|
BLAKE2b-256 checksum How to use checksums |
41c9b932892f94c79634748274cbbe5a8f707c50935cd33e2ca6c8a609ec7c31
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for vereqsyn 1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.