issue_comments: 739576721
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/3929#issuecomment-739576721 | https://api.github.com/repos/pydata/xarray/issues/3929 | 739576721 | MDEyOklzc3VlQ29tbWVudDczOTU3NjcyMQ== | 1217238 | 2020-12-06T22:36:32Z | 2020-12-06T22:36:32Z | MEMBER | It sounds like making this work well would require xarray to support "unknown" dimension sizes throughout the codebase. This would be a nice feature to have, but indeed would likely require pervasive changes. The other option would be to explicitly compute the shape when converting from dask dataframes, by calling |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
593029940 |