Deprecate cv_values_ in favour of cv_results_ in RidgeCV estimators
#28915
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
reviewed
Apr 30, 2024
There was a problem hiding this comment.
Thanks for the PR @lucyleeow . Also need to trigger a doc build to make sure we don't have this in our docs.
adrinjalali
approved these changes
May 2, 2024
jeremiedbb
approved these changes
May 2, 2024
|
Thanks for the review! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference Issues/PRs
closes #7206
What does this implement/fix? Explain your changes.
Deprecate
cv_values_andst 8000 ore_cv_valuesinRidgeCVandRidgeClassifierCVAny other comments?