lilyponddist
This package wraps the binary distribution of lilypond, allowing to install and use lilypond from python
Notice that this package installs lilypond from the releases provided by the lilypond team. It does not conflict with any user-installed lilypond version, since it places lilypond at an ad-hoc place, without modifying the PATH or any other part of the environment.
At the moment these platforms are supported: linux-x86_64, windows-x86_64, darwin-x86_64 and darwin-arm64.
The first time it is asked for the path of the lilypond binary, lilyponddist will download the given version (or the latest version if no version is specified) and the user can call that binary as if it was any regular installation of lilypond. Any subsequent call will use the already installed version.
lilyponddist follows the release process of lilypond closely and any new binary release is incorporated to the registry of downloads. Updating lilyponddist through pip will make these updates available via the update function.
Installation
pip install lilyponddist
Example
import lilyponddist
import subprocess
subprocess.call([lilyponddist.lilypondbin(), '/path/to/score.ly', '--pdf', '-o', '/path/to/output'])
Documentation
### lilypondbin(version='')
### update()
Update the current lilypond installation if possible
### can_update()
Checks if an update is available. This functions will return the latest version to update to, or None if there are no updates available
# The current version can be checked via lilypond_version. This returns the version of the # lilypond distribution installed via lilyponddist. There is never an attempt to interact with # a user installed lilypond lilyponddist.lilypond_version()
# All available versions can be queried via lilyponddist.avaialable_versions()
# Installed versions can be queried via lilyponddist.installed_versions()
Metadata
Release files for lilyponddist 1.2.3.22581
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 |
|---|---|---|---|---|
| lilyponddist-1.2.3.22581.tar.gz | 15.2 kB | Without provenance | Details for lilyponddist-1.2.3.22581.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lilyponddist-1.2.3.22581-py3-none-any.whl | Python 3 | none | any | Details for lilyponddist-1.2.3.22581-py3-none-any.whl |
Total release size: 26.2 kB
Release files / lilyponddist-1.2.3.22581.tar.gz
| Download URL | lilyponddist-1.2.3.22581.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbb58cf1b869b209668a8ea5b442b0dc636b5ff31df2ac1a42cacf741ea71104
|
|
BLAKE2b-256 checksum How to use checksums |
f2230dcaa255409d7079b6575f9f5cf2fff3c5768d10afd64c3467f2482b3ec0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.22
|
Release files / lilyponddist-1.2.3.22581-py3-none-any.whl
| Download URL | lilyponddist-1.2.3.22581-py3-none-any.whl |
|---|---|
| Size | 11.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f39bb350da47c012c038ae187ffa3a03c882f8f98c4ab72e19b1a2f5b4b0791
|
|
BLAKE2b-256 checksum How to use checksums |
12746a23eba076a896fc2b8d229d7633f2a217e050b3f9c4b8ec2ba39dd213b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.22
|
Security for lilyponddist 1.2.3.22581
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.