I refactored the repo to separate ROS1 from ROS2 in two different sub-packages. By default jupyros still export everything from ros1, and at the moment, ros2 re-exports everything from ros1.
I'm not sure if we should create the ros1 folder. My idea is to prevent ROS2 users to import something that doesn't work on ROS2 by mistake.
With this organization, we can still import ROS1 as a default using:
import jupyros or from jupyros import ros3d
And at the same time have a separate package for ROS2:
from jupyros import ros2 or from jupyros.ros2 import ros3d
@wolfv
I refactored the repo to separate ROS1 from ROS2 in two different sub-packages. By default jupyros still export everything from ros1, and at the moment, ros2 re-exports everything from ros1. I'm not sure if we should create the ros1 folder. My idea is to prevent ROS2 users to import something that doesn't work on ROS2 by mistake.
With this organization, we can still import ROS1 as a default using:
import jupyrosorfrom jupyros import ros3dAnd at the same time have a separate package for ROS2:from jupyros import ros2orfrom jupyros.ros2 import ros3d