You don't need to install virtualenv, you can create a venv with python -m venv then activate the venv then pip install the dependencies
There is one other possible problem with the -U in that pip command. It may or may not work. The -U option used to be used for installing packages userwide (instead of system wide), but bookworm made away with that too.
Try it. If it does not work, skip the -U, which will install the package in the venv only and whatever other binaries need it will require to have the venv activated too in their own processes before they can find the packages.
In other words, the repo you are trying to use does not seem ready for primetime using bookworm yet. Those things need to be worked out, or you can downgrade to Buster and the repo's instructions should work exactly as written.
If you want to stick with bookworm, good luck working with the repo's guys. It really is up to them to figure out how to support their stuff on new OSes.
My advice is that if you really want to use the stuff in that repo, downgrade to Buster or whatever other version they tell you you should use.
Code:
python3 -m venv venvsource ./venv/bin/activatepip install <whatever packages you need like the grpcio>Try it. If it does not work, skip the -U, which will install the package in the venv only and whatever other binaries need it will require to have the venv activated too in their own processes before they can find the packages.
In other words, the repo you are trying to use does not seem ready for primetime using bookworm yet. Those things need to be worked out, or you can downgrade to Buster and the repo's instructions should work exactly as written.
If you want to stick with bookworm, good luck working with the repo's guys. It really is up to them to figure out how to support their stuff on new OSes.
My advice is that if you really want to use the stuff in that repo, downgrade to Buster or whatever other version they tell you you should use.
Statistics: Posted by memjr — Sat Feb 10, 2024 6:56 am