-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
MNT Remove HistGradientBoosting from experimental #19799
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.
thanks @NicolasHug for this tedious search and replace :)
Co-authored-by: Jérémie du Boisberranger <34657725+jeremiedbb@users.noreply.github.com>
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 I found a solution to the doc build failure, but I'm not familiar with sphinx so it might not be that at all :)
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. Thanks @NicolasHug !
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.
Nitpick + question of backward compatibility.
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. @NicolasHug Thank you. Finally, HGBT becomes stable. I hope that this helps to get more widely used.
Closes #19792
The last obstacle to make these estimators stable was #18894. The preferred solution has not ETA yet and should be backward compatible anyway, so it's not worth delaying the "stabilization" of the estimators any longer.
importing
enable_hist_gradient_boosting
now throws a warning - no strong opinion, but it's probably better to encourage users to remove the imports, hence the warning.for ref: