mopidy-somafm
Mopidy extension for SomaFM
Installation
Install by running:
python3 -m pip install mopidy-somafm
See https://mopidy.com/ext/somafm/ for alternative installation methods.
Configuration
Before starting Mopidy, you must add configuration for mopidy-somafm to your Mopidy configuration file:
[somafm]
encoding = aac
quality = highest
encodingmust be eitheraac,mp3oraacpqualitymust be one ofhighest,fast,slow,firewall
If the preferred quality is not available for a channel, the extension will fallback
to fast. And afterwards if the preferred encoding is not available for that
quality, it will fallback to using mp3.
It seems that all channels support the combination fast + mp3
You can also choose to use the channel DJ as the reported track artist (default behavior)::
[somafm]
dj_as_artist = true
Project resources
Development
Set up development environment
Clone the repo using, e.g. using gh:
gh repo clone AlexandrePTJ/mopidy-somafm
Enter the directory, and install dependencies using uv:
cd mopidy-somafm/
uv sync
Running tests
To run all tests and linters in isolated environments, use tox:
tox
To only run tests, use pytest:
pytest
To format the code, use ruff:
ruff format .
To check for lints with ruff, run:
ruff check .
To check for type errors, use pyright:
pyright .
Setup before first release
Before the first release, you must enable trusted publishing on
PyPI
so that the release.yml GitHub Action can create the PyPI project and publish
releases to PyPI.
When following the instructions linked above, use the following values in the form at PyPI:
- Publisher: GitHub
- PyPI project name:
mopidy-somafm - Owner:
AlexandrePTJ - Repository name:
mopidy-somafm - Workflow name:
release.yml - Environment name:
pypi(must match environment name inrelease.yml)
Making a release
To make a release to PyPI, go to the project's GitHub releases page and click the "Draft a new release" button.
In the "choose a tag" dropdown, select the tag you want to release or create a
new tag, e.g. v0.1.0. Add a title, e.g. v0.1.0, and a description of the changes.
Decide if the release is a pre-release (alpha, beta, or release candidate) or should be marked as the latest release, and click "Publish release".
Once the release is created, the release.yml GitHub Action will automatically
build and publish the release to
PyPI.
Credits
- Original author: Alexandre Petitjean
- Current maintainer: Alexandre Petitjean
- Contributors
Metadata
Release files for mopidy-somafm 2.1.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 | |
|---|---|---|---|
| mopidy_somafm-2.1.0.tar.gz | 14.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mopidy_somafm-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.0 kB
Release files / mopidy_somafm-2.1.0.tar.gz
| Download URL | mopidy_somafm-2.1.0.tar.gz |
|---|---|
| Size | 14.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
77bcabde36d9dbc4a3e48d3a8b7e31bf166d5e7ca75b97faf887a6e6543a119e
|
|
BLAKE2b-256 checksum How to use checksums |
c2f010f14a661cce539d0d46611b2c283e38530591c2a811eab7fc954fb9e9bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 27, 2026.
Transparency logRelease files / mopidy_somafm-2.1.0-py3-none-any.whl
| Download URL | mopidy_somafm-2.1.0-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84f4864c8050c30c4af2968585cafcf97290a40b1cfd9cc14b4d0e4582754fe0
|
|
BLAKE2b-256 checksum How to use checksums |
7a800010a1403ad5f39e649ed773c3f2cf718d907041b50613f409739702ff2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 27, 2026.
Transparency log