You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
High Priority: the docstrings in their current form are fairly haphazard, it is important to complete this task.
Currently we define docstrings for the Python API within the source code for the pybind11 python bindings example. This task involves migrating the docstrings to header files.
I think it will be difficult to maintain the docs in the bindings. So, I started playing with https://github.com/pybind/pybind11_mkdoc during the weekend to auto-generate the docs from the header files, I did also port the robot_state binding one JafarAbdi@85b1f99. What do you think of this (cc @rhaschke)? I'm more than happy to port the other files.
@JafarAbdi I am not sure if you wish to follow up on this issue yourself, I am posting here for tracking purposes. I think this should be addressed in a separate pr to the current one. What are your thoughts?
The text was updated successfully, but these errors were encountered:
This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.
github-actionsbot
added
the
stale
Inactive issues and PRs are marked as stale and may be closed automatically.
label
Apr 3, 2023
JafarAbdi
added
persistent
Allows issues to remain open without automatic stalling and closing.
and removed
stale
Inactive issues and PRs are marked as stale and may be closed automatically.
labels
May 23, 2023
Background
High Priority: the docstrings in their current form are fairly haphazard, it is important to complete this task.
Currently we define docstrings for the Python API within the source code for the pybind11 python bindings example. This task involves migrating the docstrings to header files.
Instructions
Follow up on this investigation by @JafarAbdi:
source
@JafarAbdi I am not sure if you wish to follow up on this issue yourself, I am posting here for tracking purposes. I think this should be addressed in a separate pr to the current one. What are your thoughts?
The text was updated successfully, but these errors were encountered: