Skip to content

Better treatment of unicode feature names in get_names #162

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

Closed

Conversation

AssafBenDavid
Copy link
Contributor

This solves issue #160

@AssafBenDavid
Copy link
Contributor Author

It appears that an unrelated test is failing here.
array_equivalent is no longer where it used to be in newer versions of pandas.
@dukebody would it make sense to replace it with np.allclose?

@dukebody
Copy link
Collaborator

dukebody commented Aug 5, 2018

@AssafBenDavid yep, your code is right, it was just that the CI was incorrectly configured and was picking a newer version of pandas that doesn't include these private methods. We should change the tests to use only public methods.

See pandas-dev/pandas#14555 for numpy alternatives.

@dukebody
Copy link
Collaborator

dukebody commented Aug 5, 2018

Merged in #165.

@dukebody dukebody closed this Aug 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants