Open elaiel opened 3 years ago
No ideas. Didn't happen to me. Just worked the first time I tried the new menu.
Did you try running sudo pip3 install
with either/both the --upgrade
or --force-reinstall
flags?
I'm not 100% sure of this but I think that if you run pip3 without sudo then it installs in ~/bin or ~/.local/bin, assuming one of those exists whereas, with sudo, it picks places like /usr/local/bin. Although I can't point to an example, it seems to me that if one uses a mixture of sudo/non sudo calls then one might potentially wind up in the situation where an old non-sudo version of something winds up blocking a newer sudo version of something. Maybe nose around your PATH and see what's where.
@elaiel there were 2 PRs that were just merged, update to the latest version and see if that fixes it.
Hi there I tried to switch from the original gcgarner/IOTstack to the Sensorlot/IOTstack, following the steps for the migration. Everthing worked till I had to run the menu.sh script. When the script was executed, I was asked if I wanted to upgrade the python packages:
I started the installation of the packages:
The module "blessed" should be available. I can run ./scripts/menu_main.py manually and it works. I als tried to manually install belssed as module using pip, pip3, as user and via sudo - same result. Also I should have the most current version of the ruamel.yaml, not sure why the version is not detected correctly. Any ideas how I solve this?