Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
doxygen for pydrake? #7915
My current workflow for writing code in pydrake is a bit cumbersome... I normally read the API in the c++ doxygen, then have the pybind code open to see what pieces of the API are currently wrapped (and how). What do we want this to look like in the future? Should we generate a separate doxygen page for pydrake? Should we be trying to make the docstring workflow the preferred approach?
For the short term, can I ask what environment you are using? Are you using an environment in which autocomplete is available?
One thing I haven't investigated is what
Would you like me to prioritize this? (It would take a few days of focused time, either for manual porting (which I do not prefer, but would be a starting point) or the route of automation (to stabilize / minimize duplication).)
That being said, would it be OK if we consolidate discussion to #7914 or this issue?