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 |
Please refer to wiki/UsingPython3.
Melodic will not be migrated, primarily as from it's supported list of platforms only Ubuntu Bionic is still supported (and the Python 2 there will be supported by Canonical for as long as needed (see Some things to know as Python 2 approaches EOL on ROS Discourse).
The first (and only) ROS 1 release to support Python 3 will be Noetic.
| | 2 | No.2 Revision |
Please refer to wiki/UsingPython3.
Melodic will not be migrated, primarily as from it's supported list of platforms only Ubuntu Bionic is still supported (and the Python 2 there will be supported by Canonical for as long as needed (see Some things to know as Python 2 approaches EOL on ROS Discourse).
The first (and only) ROS 1 release to support Python 3 will be Noetic.Noetic (see ros-infrastructure/rep#202).
| | 3 | No.3 Revision |
Please refer to wiki/UsingPython3.
Melodic will not be migrated, primarily as from it's supported list of platforms only Ubuntu Bionic is still supported (and the Python 2 there will be supported by Canonical for as long as needed (see Some things to know as Python 2 approaches EOL on ROS Discourse).
The first (and only) ROS 1 release to support Python 3 will be Noetic (see ros-infrastructure/rep#202).
Additional links:
Duplicates/related Q&As:
| | 4 | No.4 Revision |
Please refer to wiki/UsingPython3.
Melodic will not be migrated, primarily as from it's supported list of platforms only Ubuntu Bionic is still supported (and the Python 2 there will be supported by Canonical for as long as needed (see Some things to know as Python 2 approaches EOL on ROS Discourse).
The first (and only) ROS 1 release to support Python 3 will be Noetic (see ros-infrastructure/rep#202).
Additional links:
Duplicates/related Q&As:
I'm trying to write some ROS code and future proof it, and I find I'm wasting a ton of time recompiling everything to support Python3. Just writing a simple 10 line script to build a bag file requires recompiling nearly every package in ROS.
depending on what you actually need there is a relatively low-overhead work-around: installing Python-only ROS packages in a Python 3 venv. See rospypi/simple:
virtualenv -p python3 venv . ./venv/bin/activate pip install --extra-index-url https://rospypi.github.io/simple/ rospy ...
no need to compile anything.
This can be made as complex as you'd like, but the more custom you make it, the more time you'll "waste" on setting things up.
For simple pub/sub, service and action work this is a nice enough work-around until Noetic is here.
| | 5 | No.5 Revision |
Please refer to wiki/UsingPython3.
Melodic will not be migrated, primarily as from it's its supported list of platforms only Ubuntu Bionic is still supported (and the Python 2 there will be supported by Canonical for as long as needed (see Some things to know as Python 2 approaches EOL on ROS Discourse).Discourse)).
The first (and only) ROS 1 release to support Python 3 will be Noetic (see ros-infrastructure/rep#202).
Additional links:
Duplicates/related Q&As:
I'm trying to write some ROS code and future proof it, and I find I'm wasting a ton of time recompiling everything to support Python3. Just writing a simple 10 line script to build a bag file requires recompiling nearly every package in ROS.
depending on what you actually need there is a relatively low-overhead work-around: installing Python-only ROS packages in a Python 3 venv. See rospypi/simple:
virtualenv -p python3 venv . ./venv/bin/activate pip install --extra-index-url https://rospypi.github.io/simple/ rospy ...
no need to compile anything.
This can be made as complex as you'd like, but the more custom you make it, the more time you'll "waste" on setting things up.
For simple pub/sub, service and action work this is a nice enough work-around until Noetic is here.
| | 6 | No.6 Revision |
Please refer to wiki/UsingPython3.
Melodic will not be migrated, primarily as from its supported list of platforms only Ubuntu Bionic is still supported (and the Python 2 there will be supported by Canonical for as long as needed (see Some things to know as Python 2 approaches EOL on ROS Discourse)).
The first (and only) ROS 1 release to support Python 3 will be Noetic (see ros-infrastructure/rep#202).
Additional links:
Duplicates/related Q&As:
I'm trying to write some ROS code and future proof it, and I find I'm wasting a ton of time recompiling everything to support Python3. Just writing a simple 10 line script to build a bag file requires recompiling nearly every package in ROS.
depending on what you actually need there is a relatively low-overhead work-around: installing Python-only ROS packages in a Python 3 venv. See rospypi/simple:
virtualenv -ppython3venv . ./venv/bin/activate-m venv venv_rospy source venv_rospy/bin/activate pip install --extra-index-url https://rospypi.github.io/simple/ rospy ...
no need to compile anything.
This can be made as complex as you'd like, but the more custom you make it, the more time you'll "waste" on setting things up.
For simple pub/sub, service and action work this is a nice enough work-around until Noetic is 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.
