-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
DOC Update Lasso class docstring _coordinate_descent.py #30911
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.
Thank you for the PR @goutam-kul !
LGTM
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 @goutam-kul!
@goutam-kul, could you please add "Fixes #30893" under the "Reference Issues/PRs" section of the PR description? This will automatically close the issue when the PR is merged. |
@virchan Mentioned the issue number in the description, thanks for the input, I will keep this in mind for my next PRs. |
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 @goutam-kul
Reference Issues/PRs
What does this implement/fix? Explain your changes.
Fixes #30893
As mentioned in #30893, in the Lasso class documentation there was an incorrect suggestion that it also supports arrays input when it doesn't.
The documentation line "If an array is passed, penalties are assumed to be specific to the targets. Hence they must correspond in number." in the Lasso docs needed to be removed or the implementation needed to updated.
For quick fix I have remove the line from the documentation, as in #11566 a good discussion was done on this topic but no conclusion was formed.