home / github / issue_comments

Menu
  • GraphQL API
  • Search all tables

issue_comments: 807111762

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/5065#issuecomment-807111762 https://api.github.com/repos/pydata/xarray/issues/5065 807111762 MDEyOklzc3VlQ29tbWVudDgwNzExMTc2Mg== 1217238 2021-03-25T17:08:09Z 2021-03-25T17:08:09Z MEMBER

Xarray knows to drop the dtype encoding after an arithmetic operation. How does that work? To me .chunk feel like a similar case: an operation that invalidates any existing encoding.

To be honest, the existing convention is quite adhoc, just based on what seemed most appropriate at the time.

https://github.com/pydata/xarray/issues/1614 is most comprehensive description of the current state of things.

We were considering saying that attrs and encoding should always use the same rules, but perhaps we should be more aggressive about dropping encoding.

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