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: 257 times
Last updated: Aug 20 '18
Failure in installing a new package on ROS2
ROS2 Windows failed to load shared library of rmw implementation
What is the recommended embedded board for ROS2?
[ROS2, rclpy] sharing global var between nodes
[Nav2] Why use Voxel layer over 2D layer for RGBD sensor?
Multiple classes that inherit from rclcpp::Node in one executable
No completion for 'ros2 run' in zsh