Skip to content

FIX Wrong method in FutureWarning: if_available #23756

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

Merged
merged 1 commit into from
Jun 27, 2022

Conversation

robna
Copy link
Contributor

@robna robna commented Jun 25, 2022

The FutureWarning that triggers when using the deprecated if_delegate_has_method proposes the non-existing method if_available as replacement. Now changed to correct name: available_if

The FutureWarning that triggers when using the deprecated if_delegate_has_method proposes the non-existing method if_available as replacement. Now changed to correct name: available_if
@thomasjpfan thomasjpfan changed the title Wrong method in FutureWarning: if_available FIX Wrong method in FutureWarning: if_available Jun 26, 2022
Copy link
Member

@thomasjpfan thomasjpfan left a 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! LGTM

@glemaitre glemaitre merged commit 4b3c02f into scikit-learn:main Jun 27, 2022
@glemaitre
Copy link
Member

Thanks @robna Merging.

ogrisel pushed a commit to ogrisel/scikit-learn that referenced this pull request Jul 11, 2022
glemaitre pushed a commit to glemaitre/scikit-learn that referenced this pull request Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants