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 |
It appears OP had multiple Python interpreters installed on his system, one of which located in /usr/local.
As that took precedence over the system-provided Python (ie: 2.7 on Ubuntu Xenial), and apt-distributed python-* packages are only installed in the default locations, including the many ROS Python packages and dependencies, various import statements failed with "No module named X".
Removing the interpreter from /usr/local was not sufficient, as there also seemed to be something wrong with the, still present, system Python 2.7 install.
Reinstallation using sudo apt install --reinstall python-minimal python2.7-minimal python2.7 python-pip seemed to have restored the system-provided Python installation to a state where things seem to have normalised sufficiently for things like rosdep and roscore to start working again.
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.
