-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
Explicit docstrings for DecisionTreeClassifier.fit and DecisionTreeRegressor.fit #7809
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
The |
cleanest way writes a new fit in each that calls super. On 3 November 2016 at 01:00, alexjiang notifications@github.com wrote:
|
That's what I though. @jnothman that's not overkill, is it? I think docs are important. |
not overkill, no. easier to read in the code too On 3 November 2016 at 06:57, Andreas Mueller notifications@github.com
|
Hi, I would like to take up the issue. |
Should both the fit functions have any change in the docString from the one in the BaseDecisionTree.fit() function? |
Please close this. |
As pointed out in #7801 the docstring for the decision tree fit is a bit vague (because it's shared). I think it would be better if they had separate, precise docstrings.
The text was updated successfully, but these errors were encountered: