-
-
Notifications
You must be signed in to change notification settings - Fork 26.4k
Deprecate cv_values_ in favour of cv_results_ in RidgeCV estimators
#28915
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
cv_values_ in favour of cv_results_cv_values_ in favour of cv_results_
cv_values_ in favour of cv_results_cv_values_ in favour of cv_results_ in RidgeCV estimators
adrinjalali
left a comment
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 for the PR @lucyleeow . Also need to trigger a doc build to make sure we don't have this in our docs.
adrinjalali
left a comment
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.
Otherwise LGTM.
cc @jeremiedbb maybe?
jeremiedbb
left a comment
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. There's just a warning message mismatch. And +1 to mark None as Hidden (we won't start a deprecation cycle in 1.7 to remove None)
|
Thanks for the review! |
Reference Issues/PRs
closes #7206
What does this implement/fix? Explain your changes.
Deprecate
cv_values_andstore_cv_valuesinRidgeCVandRidgeClassifierCVAny other comments?