Fix FutureWarning: Function get_feature_names is deprecated #216
Conversation
This file contains 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
alexis-cvetkov
changed the title
LilianBoulard
approved these changes
Oct 12, 2021
|
LGTM. Merging |
This was referenced Jun 8, 2022
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.
Fix the Future Warnings mentioned in #213. Everywhere
get_feature_nameswas used (mostly in GapEncoder and some tests), we now check the version of sklearn and useget_feature_names_outifsklearn_version >= 1.0.I also added
get_feature_names_outmethods in the GapEncoder and SuperVectorizer (they simply copyget_feature_names) to override the inherited methods from sklearn.