-
-
Notifications
You must be signed in to change notification settings - Fork 25.2k
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
API deprecate penalty='none' for LogisticRegression #23877
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! You also need a changelog entry in doc/whats_new/v1.2.rst
.
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
…nto api/lr-penalty
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
Co-authored-by: Tom Dupré la Tour <tom.dupre-la-tour@m4x.org>
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.
Codewise, this LGTM.
As for deprecating "none", I prefer to wait for another maintainer's opinion before merging. I feel like deprecating and removing "none" will impact a lot of users. A more conservative option would be to support both options.
Overall, I am +1 with the deprecation.
I agree we could avoid a deprecation cycle by supporting both "none" and None. No strong opinion, let's say we accept both options in this case, to avoid messing with existing code calling |
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.
A deprecation cycle is fine IMO.
Thanks @MaxwellLZH |
Reference Issues/PRs
Fixes #23749.
What does this implement/fix? Explain your changes.
This PR deprecates
penalty='none'
for LogisticRegression, so the usage ofpenalty=None
is consistent amongSGDClassifier
,SGDRegressor
,Perceptron
andLogisticRegression
.