-
-
Notifications
You must be signed in to change notification settings - Fork 26.3k
DOC ensures DBSCAN docstring passes numpydoc validation #20375
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
Conversation
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.
Otherwise LGTM.
This looks great, thanks for the feedback! |
Co-authored-by: Guillaume Lemaitre <[email protected]>
Co-authored-by: Guillaume Lemaitre <[email protected]>
@glemaitre is there a way to re-run the CI without doing something like an empty commit? It seems like a step failed due to timeout |
@fbidu The failure is unrelated (just a timeout of one of the mac build). Everything is alright. Merging. Thanks |
…#20375) Co-authored-by: Iván Pulido <[email protected]> Co-authored-by: Guillaume Lemaitre <[email protected]>
Reference Issues/PRs
Addresses #20308
What does this implement/fix? Explain your changes.
This PR makes dbscan compatible with numpydoc
Any other comments?
cc: @ijpulidos