-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
[MRG] MAINT Use check_scalar in _BaseVoting #22204
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
[MRG] MAINT Use check_scalar in _BaseVoting #22204
Conversation
This reverts commit ae4698c.
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.
Apart from the unnecessary checks on n_jobs
, LGTM.
Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
Co-authored-by: Olivier Grisel <olivier.gr 8000 isel@ensta.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.
LGTM
Hi @ogrisel! I believe this one is ready for merge. Unnecessary checks have been removed. |
The last failure was addressed in |
Reference Issues/PRs
Addresses #20724 and #21927
#DataUmbrella
What does this implement/fix? Explain your changes.
Summary of changes to
voting
estimators:_BaseVoting
,VotingClassifier
, andVotingRegressor
.check_scalar
fromsklearn.utils
to validate the parameters.Test and validation progress:
In both estima 8000 tors
In VotingClassifier
References
Any other comments?
Please advise correct type/range if different than what I have below. (Thank you):
param: type-> range
n_jobs
: int-> (-inf, -1] or [1, int), or None (not including 0)verbose
: int-> [0, inf), or np.bool_flatten_transform
: int-> (-inf, inf), or np.bool_