-
Notifications
You must be signed in to change notification settings - Fork 845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix a few broken docstrings #6480
Conversation
- Python keywords should not be used as parameter names
@greglandrum the failure here is due to the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the MHFP thing has a simpler solution.
yep, I was doing the review as you sent this gentle reminder. :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* - Fix a couple of docstrings that were confusing boost::python - Python keywords should not be used as parameter names * changes in response to review * removed two leftover BOOST_PYTHON_FUNCTION_OVERLOADS --------- Co-authored-by: Tosco, Paolo <paolo.tosco@novartis.com>
boost::python
(FromArray, FromStringArray); namely, the comment was being parsed as the parameter name, i.e.:FromArray((MHFPEncoder)vec, (list)Creates a MHFP vector from a list of unsigned integers.) →
_vectj
FromStringArray(_(MHFPEncoder)vec, (list)Creates a MHFP vector from a list of arbitrary strings.) →
_vectj
from
)