Homebrew extensions not showing up in deps

I have just worked through getting mopidy running on my MBP (see Mopidy won't start: No package metadata was found for Mopidy · Issue #46 · mopidy/homebrew-mopidy · GitHub) and now I’m looking to interact with it. I used brew to install it, and have also installed extensions that way:

But they don’t show up in deps here below. Is there some other way to get them installed? I’m pretty sure (multiple sources) said to use brew to install, and it looks like they are. So why don’t they show in deps?

$ mopidy deps

WARNING  2025-05-10 16:59:44,699 [37872:MainThread] mopidy.config
  Ignoring config section 'local' because no matching extension was found
Executable: /usr/local/bin/mopidy
Platform: macOS-15.4.1-x86_64-i386-64bit
Python: CPython 3.12.10 from /usr/local/Cellar/python@3.12/3.12.10/Frameworks/Python.framework/Versions/3.12/lib/python3.12
Mopidy: 3.4.2 from /usr/local/Cellar/mopidy/3.4.2/libexec/lib/python3.13/site-packages
  Pykka: 3.1.1 from /usr/local/Cellar/mopidy/3.4.2/libexec/lib/python3.13/site-packages
  requests: 2.31.0 from /usr/local/Cellar/mopidy/3.4.2/libexec/lib/python3.13/site-packages
    charset-normalizer: 3.3.2 from /usr/local/Cellar/mopidy/3.4.2/libexec/lib/python3.13/site-packages
    idna: 3.3 from /usr/local/Cellar/mopidy/3.4.2/libexec/lib/python3.13/site-packages
    urllib3: 1.26.18 from /usr/local/Cellar/mopidy/3.4.2/libexec/lib/python3.13/site-packages
    certifi: 2025.4.26 from /usr/local/lib/python3.12/site-packages
  setuptools: 80.2.0 from /usr/local/lib/python3.12/site-packages
  tornado: 6.4 from /usr/local/Cellar/mopidy/3.4.2/libexec/lib/python3.13/site-packages
GStreamer: 1.26.1.0 from /usr/local/lib/python3.12/site-packages/gi
  Detailed information: 
    Python wrapper: python-gi 3.52.3
    Relevant elements:
      Found:
        uridecodebin
        souphttpsrc
        appsrc
        oss4sink
        id3demux
        id3v2mux
        lamemp3enc
        mpegaudioparse
        mpg123audiodec
        vorbisdec
        vorbisenc
        vorbisparse
        oggdemux
        oggmux
        oggparse
        flacdec
        flacparse
        shout2send
      Not found:
        alsasink
        osssink
        pulsesink
        flump3dec
        mad

I have tried reinstalling the brew formulae for these extensions, and also tried using a virtual environment for python3 to run mopidy in. Unfortunately mopidy doesn’t run in the virtual envrionment:

$ mopidy

ERROR: A GObject based library was not found.

Mopidy requires GStreamer to work. GStreamer is a C library with a
number of dependencies itself, and cannot be installed with the regular
Python tools like pip.

Please see https://docs.mopidy.com/en/latest/installation/ for
instructions on how to install the required dependencies.

ModuleNotFoundError: No module named 'gi'

So going back to the mopidy installed with brew that mostly works, I tried installing an extension with pip3. This is the new python3 push for the virtual environment that I often use but here I’m stuck I think because some things are brew installed (main mopidy) and some then in the virtual env are installed with pip3.

So should I uninstall all of brew mopidy?

$ pip3 install Mopidy-Local
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try brew install
    xyz, where xyz is the package you are trying to
    install.
    
    If you wish to install a Python library that isn't in Homebrew,
    use a virtual environment:
    
    python3 -m venv path/to/venv
    source path/to/venv/bin/activate
    python3 -m pip install xyz
    
    If you wish to install a Python application that isn't in Homebrew,
    it may be easiest to use 'pipx install xyz', which will manage a
    virtual environment for you. You can install pipx with
    
    brew install pipx
    
    You may restore the old behavior of pip by passing
    the '--break-system-packages' flag to pip, or by adding
    'break-system-packages = true' to your pip.conf file. The latter
    will permanently disable this error.
    
    If you disable this error, we STRONGLY recommend that you additionally
    pass the '--user' flag to pip, or set 'user = true' in your pip.conf
    file. Failure to do this can result in a broken Homebrew installation.
    
    Read more about this behavior here: <https://peps.python.org/pep-0668/>

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

Did you create your virtualenv with --system-site-package else it can’t see your gstreamer installation

1 Like

thank you!!! That was the perfect fix for me!

Now I have mopidy-local and mopidy-mpd deps and no warning anymore for the local extension.

Now I just need to learn how to use mopidy. LOL… I’ll go RTFM a bit more