Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace (py)liblo(3) #338

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from
Open

Conversation

s0600204
Copy link
Contributor

@s0600204 s0600204 commented Jan 3, 2025

This first commit of this PR removes pyliblo/pyliblo3 (and its liblo dependency) and replaces it with python-osc (https://github.com/attwad/python-osc).

This has a number of advantages, namely:

  1. python-osc is pure-python, thus removing a non-python dependency (and making cross-platform implementation of LiSP easier)
  2. It's easier to obtain (than pyliblo) (at least from pip, if not currently from system repositories)
  3. It's maintained (if not actively developed) (unlike pyliblo), and the versions are tagged (unlike pyliblo3)

The second commit rewrites the OSC plugin's application-level configuration page to (hopefully) make it easier to understand for users. Not strictly pertinent to replacing the OSC library, but as I was working in the area...

What isn't included in this PR:

  • A rebuilt lockfile
  • An updated flatpak specification

This is a pure-python implementation, *is actually maintained*, and is a lot
easier to install than liblo/pyliblo/pyliblo3

...although admittedly it's not in debian[-based] repos (yet).

See:
* https://github.com/attwad/python-osc
* https://python-osc.readthedocs.io/en/latest/index.html
* https://pypi.org/project/python-osc/
* https://repology.org/project/python:python-osc/versions
To make it easier to comprehend what the values are used for
As the new library doesn't tell us what the argument types are,
we derive them ourselves.
@FrancescoCeruti FrancescoCeruti self-assigned this Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants