Skip to content

BUG: Added new names for pandas isna/notna unary functions #1664

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
wants to merge 1 commit into from

Conversation

gerritholl
Copy link
Contributor

In pandas commit
pandas-dev/pandas@7930202
isna and notna were added as aliases for isnull and notnull. Those need
to be added to PANDAS_UNARY_FUNCTIONS for xarray datasets notnull to work.
Closes #1663.

Note: I'm not sure how to test for this, as I think existing tests should be already failing due to this. In fact, when I run nosetests on my system I get 123 skips, 29 errors and 2 failures, none of which are related to my addition, so there must be something wrong on my system.

I did not try the flake8 test and I think new documentation is exaggerated in this case.

In pandas commit
pandas-dev/pandas@7930202
isna and notna were added as aliases for isnull and notnull.  Those need
to be added to PANDAS_UNARY_FUNCTIONS for xarray datasets notnull to work.
Closes pydata#1663.
@shoyer
Copy link
Member

shoyer commented Oct 27, 2017

I am happy to add isna/notna methods to xarray, but we don't need them to fix #1663 which is already resolved on xarray master.

@shoyer shoyer closed this Nov 9, 2017
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants