Chord Progressions
A library for working with chord progressions.
Installation
Requires Python 3.12 or newer.
pip install chord-progressions
Usage
See documentation at https://p3zo.github.io/chord-progressions.
Development
Configuration for local development with Docker is provided. Run make build to build the container, make shell to
get a shell inside of it for ad-hoc usage, and make test to run all unit tests inside the container. See
the Makefile for all available actions.
To upgrade the version and trigger a new release, use bump-my-version bump minor chord_progressions/__init__.py.
The documentation uses Material for MkDocs to build a static site from
Markdown files. Use mkdocs serve to start a live preview server of the site that automatically rebuilds upon saving.
Build the site with mkdocs build and deploy with mkdocs gh-deploy.
1 maintainer
Metadata
1 maintainer
Release files for chord-progressions 0.38.0
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 |
|---|---|---|---|---|
| chord_progressions-0.38.0.tar.gz | 29.3 kB | With provenance | Details for chord_progressions-0.38.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chord_progressions-0.38.0-py3-none-any.whl | Python 3 | none | any | Details for chord_progressions-0.38.0-py3-none-any.whl |
Total release size: 58.4 kB
Release files / chord_progressions-0.38.0.tar.gz
| Download URL | chord_progressions-0.38.0.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18db015aacd6f56f8485b0957c1c63faa8899404fdea15fc18b2515944c1209b
|
|
BLAKE2b-256 checksum How to use checksums |
86c12a9da4bc74b5bfec8e96c6a6e2234308235128bf9c665aacc522c0ce9f56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logRelease files / chord_progressions-0.38.0-py3-none-any.whl
| Download URL | chord_progressions-0.38.0-py3-none-any.whl |
|---|---|
| Size | 29.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6988d003ca2d4dcbec65451f8ed416a7804ad33eefa5b8a5524c7a4326b8bffa
|
|
BLAKE2b-256 checksum How to use checksums |
57ea6ddc11a8ad00506a0ac7737a62764a46d3fe9df5656b5e970992fa998062
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logSecurity for chord-progressions 0.38.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for chord_progressions-0.38.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 2, 2026.
Transparency logA 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.
