DOC remove FutureWarnings from release 1.1.0 #24939
Merged
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
…_init (KMeans) for plot_release_highlights_1_1_0.py
|
The changes are good. Thanks @edenies |
25 tasks
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
Fixes the task release_highlights/plot_release_highlights_1_1_0.html of the issue #24876 .
What does this implement/fix? Explain your changes.
This PR fixes the FutureWarning linked to usage of
KMeanswithoutn_initexplicitly defined. Therefore I addedn_init="auto"(previous default value) making the Depreciation Warning go away.Moreover, a FutureWarning occured with the usage of
sparsewhen callingOneHotEncoderwhich was renamed tosparse_output.Any other comments?