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.
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
FIX support scalar values in fit_params in SearchCV #15863
FIX support scalar values in fit_params in SearchCV #15863
Changes from 8 commits
0492836
1ae9d03
341f8e0
53d7a91
ef64f0b
d5f0ba0
9567b44
f340ab6
ffb7ce5
2b5b1db
ffbac6f
c0216dc
4693729
d7a2c19
52ecee4
be69ce0
9b71a9c
46c4b9f
71fab3f
9a85162
f41c808
c989c70
570dfa8
444c947
9f47b58
75bd0a9
c24f39d
63679fd
849615b
7837cdf
b98e194
3127d2b
a096a7d
18b1207
74d70e7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
do we have to convert to csr? I think if the estimator needs to convert the param, they'll do it themselves.
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.
For backward-compatibility only (we were doing it before). I assume that
csr
would be a good default since we are converting tocsr
when the number of samples in the arrays are the same than inX
meaning that we should be efficient takingrows
.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.
Sorry if I've missed something, but if the point is not to pass anything which implements
__array_function__
, shouldn't we test for that instead? An object may implement that protocol and implement__getitem__
, can it not?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.
So you mean something like:
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.
yeah this looks better. I'd put the
__array_function__
condition on top or right aftersp.issparse
though.