You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we migrate to ROS 2 (uf-mil/mil#1124), we will need to find a suitable replacement for asynchronous operations in ROS 2. There are a few ways we could go about this:
We could re-implement the features of axros in ROS 2, and barely change the public API of this library.
We can use some of the partial-async compatible features in rclpy rather than continuing development of axros
We can try to convert as much of our code using asyncio to use threads instead
We could develop async wrappers around rclpy and publish those as part of axros2
The direction of this library will have to be determined with time. Relevant issues:
As we migrate to ROS 2 (uf-mil/mil#1124), we will need to find a suitable replacement for asynchronous operations in ROS 2. There are a few ways we could go about this:
axros
in ROS 2, and barely change the public API of this library.rclpy
rather than continuing development ofaxros
asyncio
to use threads insteadrclpy
and publish those as part ofaxros2
The direction of this library will have to be determined with time. Relevant issues:
Most of these issues just contain workarounds to make
asyncio
work with the existing implementation ofrclpy
.The text was updated successfully, but these errors were encountered: