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?
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?
Please start posting anonymously - your entry will be published after you log in or create a new account.
Asked: 2018-08-19 13:29:30 -0600
Seen: 76 times
Last updated: Aug 20 '18
ROS 2 Bouncy : Node, Log and Classes best practice
[ros2cli] How can I get launch files?
[ROS2] What's the best way to wait for a new message?
[ros2cli] Cannot get the lifecycle state of lifecycle demo nodes?
How to call spin_some or spin_until_future_complete in member functions
ROS on Windows: Subsystem for Linux, ROS 2 or ROS with Docker on Windows
Buildfarm - Failing to find dependencies