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

Librosa import just stops and does nothing #1620

Closed
DorianCreuze opened this issue Dec 10, 2022 · 5 comments
Closed

Librosa import just stops and does nothing #1620

DorianCreuze opened this issue Dec 10, 2022 · 5 comments
Labels
question Issues asking for help doing something Upstream/dependency bug Another package is causing us trouble!

Comments

@DorianCreuze
Copy link

DorianCreuze commented Dec 10, 2022

I import librosa in my program using the following line
import librosa

and when I run my program it just stops there and does nothing, there is no error message so I can't give you any

here you see a screen shot of the beginning of my program and the output window
and as you can see the import librosa stop everything
p

if you need more info just ask them

thank you

@lostanlen
Copy link
Contributor

Thanks. How did you install librosa? Are you using a virtual environment?

I see you're using Windows 10 ... can you try import numba; numba.__version__ ?

@DorianCreuze
Copy link
Author

sorry I forgot to write a pretty important par, i'm using visual studio 2022.
numba's version is 0.56.4

@bmcfee
Copy link
Member

bmcfee commented Dec 12, 2022

Sounds like a duplicate of #1576

IIRC the solution was that the user had installed librosa to a directory where there were no write permissions, so the numba cache could not be constructed. The numba documentation should be helpful here if you want to change the cache path to something where you definitely have write access.

Note that importing numba would not be enough to detect this problem - you'd need to jit compile a function with caching enabled.

@bmcfee bmcfee added question Issues asking for help doing something Upstream/dependency bug Another package is causing us trouble! labels Dec 12, 2022
@bmcfee
Copy link
Member

bmcfee commented Dec 13, 2022

Side note: if @DorianCreuze can confirm that this was the problem, it's probably worth adding an entry to the troubleshooting section of the docs to talk about this.

@bmcfee
Copy link
Member

bmcfee commented Jan 16, 2023

Closing this out after a month with no activity. Feel free to reopen if the diagnosis above turns out to be incorrect.

@bmcfee bmcfee closed this as completed Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Issues asking for help doing something Upstream/dependency bug Another package is causing us trouble!
Development

No branches or pull requests

3 participants