lytk 0.1.0__tar.gz

lytk-0.1.0/.cargo/config.toml

@@ -0,0 +1,7 @@
+# pyo3 is built with the "extension-module" feature, which intentionally does
+# not link libpython. On macOS the linker then rejects the undefined Python
+# symbols when building the `cargo test` harness. These flags let macOS resolve
+# them lazily at runtime (dynamic lookup). Our Rust tests never call into Python,
+# so the symbols are never actually invoked. Linux/Windows link fine without this.
+[target.'cfg(target_os = "macos")']
+rustflags = ["-C", "link-arg=-undefined", "-C", "link-arg=dynamic_lookup"]

lytk-0.1.0/.gitignore

@@ -0,0 +1,56 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+.vscode/
+
+# Scratch / test output files (root-level only)
+/out.xml
+/example.xml
+/pedal.xml
+/rep.xml
+/test*.ly
+/test*.midi
+/test*.pdf
+
+# Virtual environments
+.venv
+lily/
+target/
+lilybert/
+lilypond/
+lilypond-export/
+MEILER/
+lilypond-midi-input/
+PDMX/
+lilypond-musicxml2ly-dev/
+oll-core/
+openlilylib/
+tree-sitter-lilypond/
+abjad/
+hum2ly/
+lilypond-rs/
+quickly/
+python-ly/
+# Anchor to repo root: these are vendored reference crates. Without the leading
+# slash, `musicxml/` also ignored `tests/fixtures/musicxml/` (a real fixture dir).
+/musicxml/
+/musicxml-std/
+symusic/
+MuseScore/
+lyp/
+music21/
+muspy/
+*.so
+
+# Proptest regression files
+*.proptest-regressions
+
+# Generated/scratch conversion outputs
+/example_*.xml
+tests/fixtures/**/*.pdf
+tests/fixtures/ly/*.midi

lytk-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,16 @@
+# See https://pre-commit.com for more information
+# See https://pre-commit.com/hooks.html for more hooks
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+    -   id: trailing-whitespace
+    -   id: end-of-file-fixer
+    -   id: check-yaml
+    -   id: check-added-large-files
+
+-   repo: https://github.com/AndrejOrsula/pre-commit-cargo
+    rev: 0.5.0
+    hooks:
+    -   id: cargo-fmt
+    -   id: cargo-clippy

lytk-0.1.0/.python-version

@@ -0,0 +1 @@
+3.10

lytk-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contributing to lytk
+
+Thanks for your interest. Bug reports with a minimal input file are especially
+welcome — most issues in this codebase are format edge cases.
+
+## Setup
+
+```bash
+cargo build                  # Rust library + CLI
+uv sync                      # Python dev environment
+maturin develop              # build the extension module into the venv
+```
+
+## Before opening a pull request
+
+```bash
+cargo fmt
+cargo clippy --all-targets -- -D warnings
+cargo test
+pytest tests/
+```
+
+`pre-commit install` wires up the formatting and clippy checks locally.
+
+## Conventions
+
+- **Tests first.** Every behaviour change needs a test that fails before the fix.
+  Round-trip tests assert *semantic* equivalence (pitches, durations, structure),
+  never string equality — emitters are free to reformat.
+- **Fixtures** live in `tests/fixtures/`. Add the smallest file that reproduces
+  the problem.
+- **New formats** go through the IR: implement `ToIrAdapter`/`FromIrAdapter` (or
+  the Layer-1 `ToMusicAdapter`/`FromMusicAdapter`) rather than converting
+  format-to-format directly. See `docs/design.md`.
+- **New transforms** implement both `Transform` and `MusicTransform`, and must be
+  idempotent and composable.
+- The PyO3 bindings live in `src/python.rs` and `src/navigation.rs`; the rest of
+  the crate stays pyo3-free so `src/lib.rs` remains a plain Rust root.
+  Python-visible changes need a matching entry in `src/lytk/_core.pyi`.
+- **Optional dependencies stay optional.** torch and TensorFlow are imported
+  inside the method that needs them, never at module scope, so `import lytk`
+  works without either. Their tests use `pytest.importorskip`.
+- A new input format needs adding to **both** `lytk.cli._SUPPORTED_EXTS` and
+  `lytk.datasets.SUPPORTED_EXTENSIONS` — `test_extensions_match_the_cli` enforces
+  that they agree.
+- `src/tree-sitter/` is vendored generated code — never edit it by hand.
+
+## Releasing
+
+lytk is distributed on **PyPI only**; the Rust crate is the implementation, not a
+published artifact.
+
+Maintainers: bump the version in both `Cargo.toml` and `pyproject.toml`, update
+`docs/changelog.md`, then push a `v*` tag. `.github/workflows/release.yml` builds
+the abi3 wheels and the sdist, gates on the test suite, and publishes to PyPI via
+Trusted Publishing.
+
+## Licence
+
+Contributions are accepted under the MIT licence of this project.