home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 631689889

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions performed_via_github_app issue
https://github.com/pydata/xarray/pull/4060#issuecomment-631689889 https://api.github.com/repos/pydata/xarray/issues/4060 631689889 MDEyOklzc3VlQ29tbWVudDYzMTY4OTg4OQ== 1217238 2020-05-20T19:50:23Z 2020-05-20T19:50:23Z MEMBER

The original motivation for requiring dask='allowed' is that I was concerned that users would put a function that coerces its arguments into NumPy arrays into apply_ufunc (e.g., like many functions from SciPy), which could have surprisingly bad performance when called on dask arrays due to automatic coercion.

Maybe this is too defensive/surprising, and could be relaxed. We don't really have any guard-rails like this elsewhere in xarray.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  618081836
Powered by Datasette · Queries took 78.575ms · About: xarray-datasette