Skip to content

workaround for failing dask zeros_like #4505

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
wants to merge 1 commit into from

Conversation

mathause
Copy link
Collaborator

@@ -101,6 +101,8 @@ def isnull(data):
return isnan(data)
elif issubclass(scalar_type, (np.bool_, np.integer, np.character, np.void)):
# these types cannot represent missing values
if hasattr(data, "_meta"):
Copy link
Contributor

Choose a reason for hiding this comment

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

We have is_duck_dask_array somewhere. But I'm not sure if pint (for e.g.) forwards the _meta property. cc @keewis

Copy link
Collaborator

Choose a reason for hiding this comment

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

pint will forward to the wrapped array using __getattr__ if it doesn't define the attribute itself, so we should be good. I'm not sure if other duck dask arrays do that, though (are there any rules/conventions for this?).

@mathause
Copy link
Collaborator Author

This might get fixed upstream dask/dask#6731 Also my idea does not seem to work...

@mathause
Copy link
Collaborator Author

This was fixed upstream. There are new failures but I am pretty sure they are unrelated as dask is not involved.

@mathause mathause closed this Oct 16, 2020
@mathause mathause deleted the try_fix_dask_zeros_like branch October 16, 2020 12:18
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.

dask dev upstream test failiures
3 participants