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.

ModuleNotFoundError: No module named 'numba.decorators'

See original GitHub issue

Describe the bug import librosa breaks on latest librosa and numba. Upstream dependency break

librosa==0.7.2 numba==0.50.0

To Reproduce

import librosa

.tox/s-py38/lib/python3.8/site-packages/librosa/util/utils.py:15: in <module>
    from .decorators import deprecated
.tox/s-py38/lib/python3.8/site-packages/librosa/util/decorators.py:9: in <module>
    from numba.decorators import jit as optional_jit
E   ModuleNotFoundError: No module named 'numba.decorators'

Workaround Pin numba in production

Issue Analytics

State:
Created 3 years ago
Reactions:37
Comments:22 (5 by maintainers)

Top GitHub Comments

112reactions

yematacommented, Jun 12, 2020

pip install numba==0.48 seems like numba removed the decorators module with version 0.50. real fix would be pinning numba version in librosa requirements

31reactions

waffletowercommented, May 4, 2022

I am sorry, but we don’t have to waste time as often on careless breakage exactly like this in other ecosystems such Java, Erlang or Swift in my direct and broad experience. My do so many tolerate Python amateur hour? Why don’t Python developers understand the concept of pinning and downstream consequences? The amount of time wasted for countless developers for inconsiderate breakage like this is staggering.

https://docs.divio.com/en/latest/how-to/resources-pin-dependencies/