ros_comm icon indicating copy to clipboard operation
ros_comm copied to clipboard

Epydoc not available on Focal -> missing Python docs for many Noetic core packages

Open peci1 opened this issue 1 year ago • 3 comments

Noetic doc jobs based on epydoc fail. E.g. https://build.ros.org/view/Ndoc/job/Ndoc__ros_comm__ubuntu_focal_amd64/50/console#console-section-7 . The docs are not generated at all: http://docs.ros.org/en/noetic/api/rospy/html/ (compare with Melodic docs ).

The most notabl package with this deficiency is rospy!

Is there any contingency plan, i.e. some magic in rosdoc_lite which would automagically switch to sphinx on Noetic?

peci1 avatar Sep 20 '22 16:09 peci1

At Clearpath, we wrote and use https://github.com/mikepurvis/catkin_tools_document to generate our internal API docs— there was a discussion back in 2019 on that project about what to do with epydoc, see: https://github.com/mikepurvis/catkin_tools_document/pull/10#discussion_r341732792

Switching to Sphinx is non-trivial since it's conceptually so different from the more auto-documenting approach of something like epydoc or doxygen. We ended up deciding to go with pydoctor, so that's what catkin_tools_document does when it encounters a call for epydoc in the rosdoc.yaml. Unfortunately I don't have a live documentation page to link you, but it's also not hard to generate a few yourself if you want to check it out.

mikepurvis avatar Oct 10 '22 02:10 mikepurvis

@mikepurvis Great you've managed to get pydoctor working, it seems a reasonable substitution for epydoc. I see catkin_tools_document is a catkin_tools-only tool, so I guees it would not be possible to easily use it in the ROS Buildfarm. Or is there a way?

peci1 avatar Oct 12 '22 10:10 peci1

This issue has been mentioned on ROS Discourse. There might be relevant details there:

https://discourse.ros.org/t/concurrency-threading-and-race-conditions-with-rospy/29659/4

ros-discourse avatar Feb 07 '23 09:02 ros-discourse