home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 1198923887

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/issues/6845#issuecomment-1198923887 https://api.github.com/repos/pydata/xarray/issues/6845 1198923887 IC_kwDOAMm_X85HdiBv 35968931 2022-07-29T06:23:59Z 2022-07-29T06:23:59Z MEMBER

My understanding is that if __array_function__ is working correctly you should never need to call cupy.round on your dataarray. Instead you should always be able to call np.round and trust that the __array_function__ implementation will dispatch to cupy's equivalent of round automatically.

Is there actually a case where we need the library-specific version of a numpy function to work too?

Do we need to update AbstractArray.array to return the underlying duck array instead of always a numpy array?

(Having said all that we might still want to make this change anyway, this was just an argument for the current behaviour being "good enough".)

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