ModuleNotFoundError: No module named 'scipy' about klippain-shaketune HOT 5 CLOSED

I also have this issue. I was using version 1.2.0 of Shake & Tune without issue up until version 2.0.0 was released. I was part of the array value to big issue that was fixed during the 2.0.0 release, but I had solved that particular issue by downgrading PiOS to the legacy distro. I will try upgrading PiOS to see if it fixes this new scipi issue.

from klippain-shaketune.

line 5: deactivate: command not found

is a venv error. Perhaps the venv didn't get activated or something.

edit:

$ python -m venv /home/pi/test
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

    apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

Failing command: ['/home/pi/test/bin/python', '-Im', 'ensurepip', '--upgrade', '--default-pip']

So when running apt-get install python3-venv and re-running install.sh in /home/pi/klippain_shaketune, it starts installing all the pip modules, including scipy.

I've restarted and running belt graph, I think this fixed it.

from klippain-shaketune.

Yes, you are running into the breaking change mentionned in the release notes of the v2.0.0. Just run the steps here and everything should work :)

Also if you are running Debian Buster (or an older system that has only Python 3.7 as the last Python version), you may need to stay on v1.x for now since this Scipy requirement apparently need to also have at least Python 3.8... I'm currently looking to mitigate this issue in order to allow older OS running Shake&Tune.

from klippain-shaketune.

Well, that doesn't install python3-venv, which apparently was missing on Debian GNU/Linux 11 (bullseye).

Also, I would kindly advise you to not instruct users to use sudo unless it absolutely required. There is no need for it on the rm command as there are no files owned other than pi. As you may know, sudo is dangerous and a mistake is easily made.

In any case, your work on this is highly appreciated! Thank you!

from klippain-shaketune.

I can confirm running the setup again fixed my issue.

from klippain-shaketune.