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 |
As a package I was using recommended python3 I tried to get ROS to work with Python3. Below I summarised my findings so others can use it as a guide when they want to use ROS with melodic.
A list of ROS distributions and their python-support status can be found here. A guide on how to use python3 with rose can be found in the UsingPython3 page of the Ros documentation.
Since at the time I started building my package the franka_ros wasn't released for melodic I had to use kinetic. However, since ROS kinetic does not fully support python3 getting the GQCNN to work under ubuntu 16.04 ROS Kinetic is not easy. I kept running into problem after problem. In the end, I decided to contribute python 2/python 3 compatibility fixed to the python 3 repositories and use python 2.7 instead. If other people really need to work with python 3 and ROS kinetic, please refer to this ros issue.
As stated in the distribution list ROS ROS Python packages starting with Melodic Morenia are highly encouraged to support both Python 2.7 and Python 3.5 or later. As a result, better ROS Melodic python 3 support is on its way. The core packages in ROS melodic are currently being ported from python 2 to python 3. An overview of which packages are already ported can be found here [REFERENCE]. If you, however, have to use a package that is not yet ported to python 3 you have to build this package from source. As explained by @gvdhoorn the procedure of doing this can be found here.
| | 2 | No.2 Revision |
As a package I was using recommended python3 I tried to get ROS to work with Python3. Below I summarised my findings so others can use it as a guide when they want to use ROS with melodic.while doing this.
A list of ROS distributions and their python-support status can be found here. A guide on how to use python3 with rose can be found in the UsingPython3 page of the Ros documentation.
Since at the time I started building my package the franka_ros wasn't released for melodic I had to use kinetic. However, since ROS kinetic does not fully support python3 getting the GQCNN to work under ubuntu 16.04 ROS Kinetic is not easy. I kept running into problem after problem. In the end, I decided to contribute python 2/python 3 compatibility fixed to the python 3 repositories and use python 2.7 instead. If other people really need to work with python 3 and ROS kinetic, please refer to this ros issue.
As stated in the distribution list ROS ROS Python packages starting with Melodic Morenia are highly encouraged to support both Python 2.7 and Python 3.5 or later. As a result, better ROS Melodic python 3 support is on its way. The core packages in ROS melodic are currently being ported from python 2 to python 3. An overview of which packages are already ported can be found here [REFERENCE]. If you, however, have to use a package that is not yet ported to python 3 you have to build this package from source. As explained by @gvdhoorn the procedure of doing this can be found here.
| | 3 | No.3 Revision |
As a package I was using recommended python3 I tried to get ROS to work with Python3. Below I summarised my findings while doing this.
A list of ROS distributions and their python-support status can be found here. A guide on how to use python3 with rose can be found in the UsingPython3 page of the Ros documentation.
Since at the time I started building my package the franka_ros wasn't released for melodic I had to use kinetic. However, since ROS kinetic does not fully support python3 getting the GQCNN to work under ubuntu 16.04 ROS Kinetic is not easy. I kept running into problem after problem. In the end, I decided to contribute python 2/python 3 compatibility fixed to the python 3 repositories and use python 2.7 instead. If other people really need to work with python 3 and ROS kinetic, please refer to this ros issue.
As stated in the distribution list ROS ROS Python packages starting with Melodic Morenia are highly encouraged to support both Python 2.7 and Python 3.5 or later. As a result, better ROS Melodic python 3 support is on its way. The core packages in ROS melodic are currently being ported from python 2 to python 3. An overview of which is core packages are already ported fully python 3 compatible can be found here [REFERENCE]. If you experience a python 2/3 incompatibility issue you can check the corresponding package repository at (https://github.com/ros)[https://github.com/ros] and file an issue. If you, however, have to use a package that is not yet ported to python 3 you have to build this package from source. As explained by @gvdhoorn the procedure of doing this can be found here.
| | 4 | No.4 Revision |
As a package I was using recommended python3 I tried to get ROS to work with Python3. Below I summarised my findings while doing this.
A list of ROS distributions and their python-support status can be found here. A guide on how to use python3 with rose can be found in the UsingPython3 page of the Ros ROS documentation.
Since at the time I started building my package the franka_ros wasn't released for melodic I had to use kinetic. However, since ROS kinetic does not fully support python3 getting the GQCNN to work under ubuntu 16.04 ROS Kinetic is not easy. I kept running into problem after problem. In the end, I decided to contribute python 2/python 3 compatibility fixed to the python 3 repositories and use python 2.7 instead. If other people really need to work with python 3 and ROS kinetic, please refer to this ros issue.
As stated in the distribution list ROS ROS Python packages starting with Melodic are highly encouraged to support both Python 2.7 and Python 3.5 or later. As a result, better ROS Melodic python 3 support is on its way. The core packages in ROS melodic are currently being ported from python 2 to python 3. An overview of which is core packages are already fully python 3 compatible can be found here [REFERENCE]. If you experience a python 2/3 incompatibility issue you can check the corresponding package repository at (https://github.com/ros)[https://github.com/ros] and file an issue. If you, have to use a package that is not yet ported to python 3 you have to build this package from source. As explained by @gvdhoorn the procedure of doing this can be found here.
| | 5 | No.5 Revision |
As a package I was using recommended python3 I tried to get ROS to work with Python3. Below I summarised my findings while doing this.
A list of ROS distributions and their python-support status can be found here. A guide on how to use python3 with rose can be found in the UsingPython3 page of the ROS documentation.
Since at the time I started building my package the franka_ros wasn't released for melodic I had to use kinetic. However, since ROS kinetic does not fully support python3 getting the GQCNN to work under ubuntu 16.04 ROS Kinetic is not easy. I kept running into problem after problem. In the end, I decided to contribute python 2/python 3 compatibility fixed to the python 3 repositories and use python 2.7 instead. If other people really need to work with python 3 and ROS kinetic, please refer to this ros issue.
As stated in the distribution list ROS ROS Python packages starting with Melodic are highly encouraged to support both Python 2.7 and Python 3.5 or later. As a result, better ROS Melodic python 3 support is on its way. The core packages in ROS melodic are currently being ported from python 2 to python 3. An overview of which is core packages are already fully python 3 compatible can be found here [REFERENCE]. If you experience a python 2/3 incompatibility issue you can check the corresponding package repository at (https://github.com/ros)[https://github.com/ros] and file an issue. If you, have to use a package that is not yet ported to python 3 you have to build this package from source. As explained by @gvdhoorn the procedure of doing this can be found here.
| | 6 | No.6 Revision |
As a package I was using recommended python3 I tried to get ROS to work with Python3. Below I summarised my findings while doing this.
A list of ROS distributions and their python-support status can be found here. A guide on how to use python3 with rose can be found in the UsingPython3 page of the ROS documentation.
Since at the time I started building my package the franka_ros wasn't released for melodic I had to use kinetic. However, since ROS kinetic does not fully support python3 getting the GQCNN to work under ubuntu 16.04 ROS Kinetic is not easy. I kept running into problem after problem. In the end, I decided to contribute python 2/python 3 compatibility fixed to the python 3 repositories and use python 2.7 instead. If other people really need to work with python 3 and ROS kinetic, please refer to this ros issue.
As stated in the distribution list ROS , ROS Python packages starting with Melodic are highly encouraged to support both Python 2.7 and Python 3.5 or later. As a result, better ROS Melodic python 3 support is on its way. The core packages in ROS melodic are currently being ported from python 2 to python 3. If you experience a python 2/3 incompatibility issue you can check the corresponding package repository at (https://github.com/ros)[https://github.com/ros] and file an issue. If you, have to use a package that is not yet ported to python 3 you have to build this package from source. As explained by @gvdhoorn the procedure of doing this can be found here.
| | 7 | No.7 Revision |
As a package I was using recommended python3 I tried to get ROS to work with Python3. Below I summarised my findings while doing this.
A list of ROS distributions and their python-support status can be found here. A guide on how to use python3 with rose can be found in the UsingPython3 page of the ROS documentation.
Since at the time I started building my package the franka_ros wasn't released for melodic I had to use kinetic. However, since ROS kinetic does not fully support python3 getting the GQCNN to work under ubuntu 16.04 ROS Kinetic is not easy. I kept running into problem after problem. In the end, I decided to contribute python 2/python 3 compatibility fixed to the python 3 repositories and use python 2.7 instead. If other people really need to work with python 3 and ROS kinetic, please refer to this ros ROS issue.
As stated in the distribution list ROS, ROS Python packages starting with Melodic are highly encouraged to support both Python 2.7 and Python 3.5 or later. As a result, better ROS Melodic python 3 support is on its way. The core packages in ROS melodic are currently being ported from python 2 to python 3. If you experience a python 2/3 incompatibility issue issue, you can check the corresponding package repository at (https://github.com/ros)[https://github.com/ros] and file an issue. If you, have to use a package that is not yet ported to python 3 you have to build this package from source. As explained by @gvdhoorn , the procedure of doing this can be found here.
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.
