Skip to content

[MRG] Feature agglomeration deprecation fix #11537

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

Conversation

amueller
Copy link
Member

Right now using feature agglomeration raises a deprecation warning. It shouldn't.

@amueller amueller changed the title Feature agglomeration deprecation fix [MRG] Feature agglomeration deprecation fix Jul 15, 2018
@amueller amueller added this to the 0.20 milestone Jul 15, 2018
@glemaitre
Copy link
Member

LGTM

Copy link
Member

@lesteve lesteve left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, good catch!

I have some memory that the check was done in the constructor at the beginning (so probably it was working originally) and then moved to fit.

@amueller
Copy link
Member Author

let's see if it passes, locally I had some weird numpy binary mismatch error and I'm rebuilding.

@amueller
Copy link
Member Author

@lesteve I figure you wanted to approve?

@glemaitre
Copy link
Member

he did :)

Copy link
Member

@qinhanmin2014 qinhanmin2014 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants