How to document ROS2 Python package source code?
What's the current best practice to document the source code of a ROS2 (Bouncy, colcon
build) Python package?
ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
What's the current best practice to document the source code of a ROS2 (Bouncy, colcon
build) Python package?
In addition to my comments in the referenced answer: The sphinx extensions should be usable without limitations, right? Means the non-default docstring styles (NumPy, Google) should be supported via napoleon
. Autogeneration via sphinx-apidoc
should be usable as well. Right?
Asked: 2018-08-19 13:29:30 -0600
Seen: 228 times
Last updated: Aug 20 '18
Failure in installing a new package on ROS2
[ROS2] Launch same node several times using same launch file
ros_control interface vs Node that publishes topics (ROS2)
MultiThreadedExecutor thread affinity for certain callbacks?
how to delete a subcriber/publisher in rclpy
ROS2 : ModuleNotFoundError: No module named ‘rclpy._rclpy’.
ROS2 Build Action Tutorial "Colcon build Failed"