1. The tooling is generic enough so that it should be helpful for migrating any ROS package, but it won't do 100% of the work. I'd recommend trying it out on the talker example from the migration guide (
https://github.com/ros2/ros2/wiki/Migration-Guide) to get a sense of the current state. We're also happy to take pull requests for new features.
2. Yes, ROS2 is targeting Python 3 (
http://design.ros2.org/articles/changes.html#c-standard) so it seemed reasonable that the migration tooling would also target Python 3.
---
[Visit Topic](
https://discourse.ros.org/t/ros1-to-ros2-migration-tools/6505/3) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)