1. Environment
- Python 3.14.7
- pip 26.2.1
2. Installation
$ pipx install spreen-tracks
(pip install spreen-tracks works too if you prefer managing the environment yourself.)
For development, install the dependencies via requirements.txt:
$ pip install -r requirements.txt
3. Execution
Run the command inside your music directory — with no options it dry-runs, printing every rename it would perform without touching a file:
$ cd ~/Music
$ track-delimiter
Target extension is `.m4a`
========== [DRY RUN] Total File Count to Clean: 4 ==========
========== [DRY RUN] The delimiters of those files will be replaced with `_` ==========
========== [DRY RUN] Start! ==========
========== [DRY RUN] Replacing the delimiter: `./Artist/Album1/1-01 Title.m4a` => `./Artist/Album1/Disc1/01_Title.m4a` ==========
========== [DRY RUN] Replacing the delimiter: `./Artist/Album1/2-01 Title.m4a` => `./Artist/Album1/Disc2/01_Title.m4a` ==========
========== [DRY RUN] Replacing the delimiter: `./Artist/Album2/01 Title.m4a` => `./Artist/Album2/01_Title.m4a` ==========
========== [DRY RUN] Replacing the delimiter: `./Artist/Album2/02 Title.m4a` => `./Artist/Album2/02_Title.m4a` ==========
========== [DRY RUN] Done! ==========
========== [DRY RUN] Total Target File Count: 4 ==========
When the plan looks right, execute it with --mode e; --extension and --delimiter override the defaults:
$ track-delimiter --mode e
$ track-delimiter --extension .mp3 --delimiter - --mode e
As a library:
from spreen_tracks import Application
Application.run() # dry run over ./**/*.m4a
Application.run(delimiter='-', mode='e') # execute the renames
4. Unit Test
$ pytest
============================= test session starts ==============================
platform linux -- Python 3.14.7, pytest-9.1.1, pluggy-1.6.0
rootdir: spreen-tracks/PyPI
configfile: pyproject.toml
collected 9 items
test/test_application.py .... [ 44%]
test/test_cli.py ..... [100%]
============================== 9 passed in 0.16s ===============================
5. Static Code Analysis
$ flake8 .
$ autoflake8 --in-place --remove-duplicate-keys --remove-unused-variables --recursive .
$ autopep8 --in-place --aggressive --aggressive --recursive .
6. Type Checks
$ mypy .
Success: no issues found in 6 source files
7. Build
$ python -m build
$ pipx install ./dist/spreen_tracks-0.1.0-py3-none-any.whl
Metadata
Release files for spreen-tracks 0.1.2
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 |
|---|---|---|---|---|
| spreen_tracks-0.1.2.tar.gz | 5.9 kB | With provenance | Details for spreen_tracks-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| spreen_tracks-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for spreen_tracks-0.1.2-py3-none-any.whl |
Total release size: 12.3 kB
Release files / spreen_tracks-0.1.2.tar.gz
| Download URL | spreen_tracks-0.1.2.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37f8dd9c2b929aa073cc91f1a29398d7a3afc96779f6e6f2ba3e97701c7e5a40
|
|
BLAKE2b-256 checksum How to use checksums |
ce6d4f0e54d0cde61716e609d34d39d934f164153d4df43b28c746818ca76640
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 6, 2026.
Transparency logRelease files / spreen_tracks-0.1.2-py3-none-any.whl
| Download URL | spreen_tracks-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a53cae75744554075ec1064b30c8559e87fc8266ecf6171676afd59a8670dfc
|
|
BLAKE2b-256 checksum How to use checksums |
8480e66441f00311131cdf0322f8cbdaa983b8cfa41137ed64db1560fc02a85e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 6, 2026.
Transparency logSecurity for spreen-tracks 0.1.2
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
Both files in this release have been uploaded with provenance metadata.
Attestation for spreen_tracks-0.1.2.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 Aug 6, 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.