The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I solved that error by the following steps, I do not know which one is essential and which one can be left out.
catking_make ... again). Not sure if that has changed anything, though. Do not forget to source.sudo apt-get install virtualenvsudo apt-get install python-pippython command uses python2.7python -m virtualenv -p python2.7 YOURVENVsource YOURVENV/bin/activate.sudo apt-get install python-scipysudo apt-get install python-rospkgpython -m pip install ... (or sudo apt-get install ..., but I did not use it)roslaunch YOURLAUNCHFILE.launch.In short:
- Uninstall concurring packages from the base and install them in the venv again.
- Re-installing the catkin workspace is not that much work in the end, that is why I would generally recommend it when in doubts about the cause of an error.
- Use sudo apt-get over pip install when possible (since apt install causes no version conflicts).
- If you use pip install, make clear which python you use with python -m pip install so that python2.7 is definitely used.
| | 2 | No.2 Revision |
I solved that error by the following steps, I do not know which one is essential and which one can be left out.
catking_make ... again). Not sure if that has changed anything, though. Do not forget to source.sudo apt-get install virtualenvsudo apt-get install python-pippython command uses python2.7python -m virtualenv -p python2.7 YOURVENVsource YOURVENV/bin/activate.sudo apt-get install python-scipysudo apt-get install python-rospkgpython -m pip install ... (or sudo apt-get install ..., but I did not use it)roslaunch YOURLAUNCHFILE.launch.In short:
- short:
Uninstall concurring packages from the base and install them in the venv again.
- again.
Re-installing the catkin workspace is not that much work in the end, that is why I would generally recommend it when in doubts about the cause of an error.
- error.
Use sudo apt-get over pip install when possible (since apt install causes no version conflicts).
- conflicts).
If you use pip install, make clear which python you use with python -m pip install so that python2.7 is definitely used.
| | 3 | No.3 Revision |
I solved that error by the following steps, I do not know which one is essential and which one can be left out.
catking_make ... again). Not sure if that has changed anything, though. Do not forget to source.sudo apt-get install virtualenvsudo apt-get install python-pippython command uses python -m virtualenv -p python2.7 YOURVENVsource YOURVENV/bin/activate.sudo apt-get install python-scipy (apt-get installs globally, but elsewise, I got errors when launching)sudo apt-get install python-rospkgpython -m pip install ... (or sudo apt-get install ..., but I did not use roslaunch YOURLAUNCHFILE.launch.In short:
Uninstall concurring packages from the base and install them in the venv again.
Re-installing the catkin workspace is not that much work in the end, that is why I would generally recommend it when in doubts about the cause of an error.
Use sudo apt-getpip install when over sudo apt-get if possible (since apt (apt install causes no version conflicts).conflicts and sometimes could help me going on, on the other hand apt-get does not care about the venv but installs globally, which is not the best approach in bigger projects. It is a bit ambiguous, see for example also comments at https://stackoverflow.com/questions/47506800/install-packages-into-virtual-environment-with-apt-get: sometimes apt-get can solve it for whatever reason...).
If you use pip install, make clear which python you use with python -m pip install so that python2.7 is definitely used.(that is somehow best practice, check python -V = 2.7 if that is needed.
| | 4 | No.4 Revision |
I solved that error by the following steps, I do not know which one is essential and which one can be left out.
catking_make ... sudo apt-get install virtualenvsudo apt-get install python-pippython command uses python2.7.python -m virtualenv -p python2.7 YOURVENV.source YOURVENV/bin/activate.sudo apt-get install python-scipy (apt-get installs globally, but elsewise, I got errors when launching)sudo apt-get install python-rospkg (same as with scipy, but better keep to an install inside your venv using pip)python -m pip install ... (or sudo apt-get install ..., but I did not use it).roslaunch YOURLAUNCHFILE.launch.In short:
Uninstall from the base any possibly concurring packages from the base that are only needed in your venv (especially those which have not been installed with sudo apt) and install them in the venv again.that are not part of the default base.
Re-installing the catkin workspace is not that much work in the end, that is why I would generally recommend it when in doubts about the cause of an error.
Use pip install over sudo apt-get if possible (apt install causes no version conflicts and sometimes could help me going on, on the other hand apt-get does not care about the venv but installs globally, which is not the best approach in bigger projects. It is a bit ambiguous, see for example also comments at https://stackoverflow.com/questions/47506800/install-packages-into-virtual-environment-with-apt-get: sometimes apt-get can solve it for whatever reason...).
If you use pip install, make clear which python you use with python -m pip install (that is somehow best practice, check python -V = 2.7 if that is needed.
| | 5 | No.5 Revision |
I solved that error by the following steps, I do not know which one is essential and which one can be left out.
catking_make catkin_make ...sudo apt-get install virtualenvsudo apt-get install python-pippython command uses python2.7.python -m virtualenv -p python2.7 YOURVENV.source YOURVENV/bin/activate.sudo apt-get install python-scipy (apt-get installs globally, but elsewise, I got errors when launching)sudo apt-get install python-rospkg (same as with scipy, but better keep to an install inside your venv using pip)python -m pip install ... (or sudo apt-get install ..., but I did not use pip2 / python -m pip, e.g. I had to install opencv-python==4.2.0.32 because the later opencv was not supported, see Python 2.7 installing opencv via pip (virtual environment). roslaunch YOURLAUNCHFILE.launch.In short:
Uninstall from the base any possibly concurring packages that are only needed in your venv (especially those which have not been installed with sudo apt) and that are not part of the default base.
Re-installing the catkin workspace is not that much work in the end, that is why I would generally recommend it when in doubts about the cause of an error.
Use pip install over sudo apt-get if possible (apt install causes no version conflicts and sometimes could help me going on, on the other hand apt-get does not care about the venv but installs globally, which is not the best approach in bigger projects. It is a bit ambiguous, see for example also comments at https://stackoverflow.com/questions/47506800/install-packages-into-virtual-environment-with-apt-get: sometimes apt-get can solve it for whatever reason...).
If you use pip install, make clear which python you use with python -m pip install (that is somehow best practice, check python -V = 2.7 if that is needed.
| | 6 | No.6 Revision |
I solved that error by the following steps, I do not know which one is essential and which one can be left out.
catkin_make ... again; source compilation). Not sure if that has changed anything, in this rospkg case, though.sudo apt-get install virtualenvsudo apt-get install python-pippython command uses python2.7.python -m virtualenv -p python2.7 YOURVENV.source YOURVENV/bin/activate.sudo apt-get install python-scipy (apt-get installs globally, but elsewise, I got errors when launching)sudo apt-get install python-rospkg (same as with scipy, but better keep to an install inside your venv using pip)python -m pip install ... (or sudo apt-get install ..., but I did not use it). In case that there are issues with the old python2.7, take the latest pip2 / python -m pipopencv-python==4.2.0.32 because the later opencv was not supported, see Python 2.7 installing opencv via pip (virtual environment). roslaunch YOURLAUNCHFILE.launch.In short:
Uninstall from the base any possibly concurring packages that are only needed in your venv (especially those which have not been installed with sudo apt) and that are not part of the default base.
Re-installing the catkin workspace is not that much work in the end, that is why I would generally recommend it when in doubts about the cause of an error.
Use pip install over sudo apt-get if possible (apt install causes no version conflicts and sometimes could help me going on, on the other hand apt-get does not care about the venv but installs globally, which is not the best approach in bigger projects. It is a bit ambiguous, see for example also comments at https://stackoverflow.com/questions/47506800/install-packages-into-virtual-environment-with-apt-get: sometimes apt-get can solve it for whatever reason...).
If you use pip install, make clear which python you use with python -m pip install (that is somehow best practice, check python -V = 2.7 if that is needed.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.