ModuleNotFoundError: No module named 'librosa'

picarica · Guru Joined: 11 Aug 2018 Posts: 326

where can i get librosa plugin? cant found it anywhere in repo, is it supported? or do i have to install it via pip

rab0171610 · Guru Joined: 24 Dec 2022 Posts: 423

You would need to install it with pip. I am not sure how others here handle python stuff that are not available through portage. The recommended method is installing to a virtual environment (venv) but I usually use the brute force method for obscure modules by using --break-system-packages. I have not had issues but others here will probably have a strong opinion about it one way or another. You will have to wait for someone else to explain what the current best practice for that is on Gentoo.

If you were wanting to do it the proper way (ebuild), I modified an existing ebuild in my localrepo for a python package. After converting it for librosa, it appears to have installed correctly.

If you have or set up a local repository for ebuilds, this worked for me using a recent version of librosa:

dev-python/librosa/librosa-0.10.2.ebuild

logrusx · Advocate Joined: 22 Feb 2018 Posts: 2421

eschwartz · Developer Joined: 29 Oct 2023 Posts: 223

pip install automatically implies --user if you run it as non-root, so the issue rarely comes up because nothing suggests that you should use "sudo pip".

(Do not ever use "sudo pip".)

That being said, the pip functionality of break-system-packages is broken and buggy by design. You need that flag even to install with --user despite that being user packages, not system packages.

You can add that option to a pip.conf configuration file so you don't need to type it in every time, though.

Hu · Administrator Joined: 06 Mar 2007 Posts: 22650

As I understand it, the Python rules for search paths mean that using pip install --user will affect the results of import lib run by that user, even when that import lib is from a system library. Thus, if you pip install --user portage==broken-version, then equery as your user will find the broken-version of portage and fail when it tries to use Portage libraries to support its query. As such, there is some value to preventing users from unknowingly installing packages into their account-level search path.

eschwartz · Developer Joined: 29 Oct 2023 Posts: 223

This is a trivially solvable problem and I have discussed it a few times with Sam/mgorny and griped a bit with upstream CPython as well.

From the Gentoo perspective, the way Gentoo packages pip and CPython to make pip behave this was was intended *solely* to prevent pip from overwriting portage managed files in /usr, and its effect on pip install --user is an unintended side effect as users are "allowed" to break their user install as long as portage run as root doesn't have issues.

It replaced a former downstream Gentoo-specific patch to pip itself that made pip error out when it detected it was run with the root UID, on the theory that using an upstream option even if it sucks and has bad side effects is better than maintaining patches.

I've now been waiting since November for an upstream PyPA project to merge patches which I need so I can improve Gentoo's gpep517 and solve this better.

(Unfortunately that involves getting PyPA to merge patches! Hence the wait times.)