issue_comments: 592847155
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/3813#issuecomment-592847155 | https://api.github.com/repos/pydata/xarray/issues/3813 | 592847155 | MDEyOklzc3VlQ29tbWVudDU5Mjg0NzE1NQ== | 1828519 | 2020-02-29T03:38:46Z | 2020-02-29T03:38:46Z | CONTRIBUTOR | @max-sixty That's exactly it. What's really weird for this is that the original code in Satpy is using a dask array and not a numpy array. It seemed very strange to both copy the DataArray ( I can understand how xarray would treat numpy arrays and dask arrays the same when it comes to this, but coming from outside the project it is very surprising that a dask array would be marked as read-only when it was used to just create a "new" numpy array. Feel free to close this or use it as a marker to clarify some documentation or error messages as mentioned in #2891. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
573031381 |