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 -0500
Seen: 251 times
Last updated: Aug 20 '18
how to organize data transfer between nodes on multiple PCs on ROS2
Nav2 lifecycle nodes don't autostart
Issue with creating a workspace (ROS2)
Using Occupancy Grids with ROS 2: frame problem and probability map
I am getting an error using Ros2 Iron and micro-ROS on RP2040
ROS vs ROS 2.0 vs ROS industrial
ROS2 Bag - DB3 CDR Deserialization