issue_comments: 696997402
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/4449#issuecomment-696997402 | https://api.github.com/repos/pydata/xarray/issues/4449 | 696997402 | MDEyOklzc3VlQ29tbWVudDY5Njk5NzQwMg== | 1217238 | 2020-09-22T21:41:01Z | 2020-09-22T21:41:01Z | MEMBER | The work around is to call The direct source of the issue here is: https://github.com/pydata/xarray/pull/4379 We probably should have been more careful with that change, because it is technically a regression. Previously we would always load data into NumPy arrays when doing a deep copy, but after that change the underlying data structures are deep-copied rather than being loaded into NumPy. That's probably more consistent with what users would expect in general from a "deep copy" but is definitely a change from the previous behavior. |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
706507153 |