Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Import paths wrong? No module named 'handlers'

See original GitHub issue

I am no Python expert, so perhaps this is a pretty simple config misstake, but I can not start mopidy.

Describe the bug Files can not be found:

pi@phoniebox:~ $ mopidy
INFO     2020-01-01 14:39:32,031 [3337:MainThread] mopidy.__main__
  Starting Mopidy 3.0.1
ERROR    2020-01-01 14:39:32,259 [3337:MainThread] mopidy.ext
  Failed to load extension iris: No module named 'handlers'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/mopidy/ext.py", line 209, in load_extensions
    extension_class = entry_point.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2417, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/local/lib/python3.7/dist-packages/mopidy_iris/__init__.py", line 7, in <module>
    import handlers
ModuleNotFoundError: No module named 'handlers'

Environment details:

OS: Raspbian Buster
Iris version Mopidy_Iris-3.43.0 installed via pip
Mopidy installed from apt-repo.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:20 (8 by maintainers)

Top GitHub Comments

1reaction

jaedbcommented, Feb 22, 2020

@s-martin this is because Mopidy doesn’t provide backwards compatibility, but mostly I simply don’t have the time resource to single-handedly manage Python 2.7/3.7 dual support.

To answer your question, you’ll need to use Iris < 34.0 until Python 3.7 is supported.

1reaction

jaedbcommented, Feb 8, 2020

@m4rc77 and @Squelsh Iris 3.44 is out in the wild now.