-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Apply numpydoc validation to docstrings #15440
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
Comments
I am working on the docstrings for |
Taking a shot at docstrings for |
I am working on the doctrings for TSNE |
looking to improve docstrings for |
working on |
working on |
Working one OneHotEncoder |
Working on |
Working on |
Working on |
Working on sklearn.cluster.MiniBatchKMeans |
Working on OrdinalEncoder |
Working on |
Worked on Lasso.path |
Working on |
Working on |
Working on |
working on VotingClassifier |
Working on |
Submitted PR for KMeans: #15473 Now working on sklearn.ensemble.AdaBoostClassifier |
working on sklearn.svm._classes.py SVC and LinearSVC classes |
I'm working on BernoulliNB. |
I'm looking at neighbors.NearestNeighbors |
RandomForestClassifier feature_importances_ is creating an error in the test_docstrings script:
We are no longer working on this estimator. |
I ran this command |
Running into a linter issue with
|
I will work on sklearn.cluster.Birch |
Picking up |
Working on OPTICS |
It would be useful to enforce docstrings style with numpydoc. Currently only a small fraction of docstring pass that validation.
To improve docstring see steps below,
Install scikit-learn from sources (see contribution guide).
install numpydoc master with,
Run the docstring validation on all docstrings,
and choose an estimator with an XFAIL status (meaning that it is a known failure). Write down all of its methods.
Run,
to see the list of validation errors for a particular method, where
import_path
can be for instancesklearn.linear_model.LogisticRegression
(for the main estimator docstring) orsklearn.linear_model.LogisticRegression.fit
(for the docstring of the fit method).Fix the docstring until validation passes. Repeat on all public methods of the chosen estimator.
Add the estimator to the whitelist in
maint_tools/test_docstrings.py
here. Note that this list accepts regular expressions, soLogisticRegression
will match all methods of that estimator, and also potentially other estimators e.g.LogisticRegressionCV
. For instance one can useLogisticRegression$
to only match the main estimator docstring. When running from step 2, checks for the modified estimators should then pass.Please write in a comment of this issue, the estimator you are planning to work on. Note that some methods are shared between estimators and are located in other files e.g.
estimator.set_params
.The text was updated successfully, but these errors were encountered: