issue_comments: 1200314984
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/2304#issuecomment-1200314984 | https://api.github.com/repos/pydata/xarray/issues/2304 | 1200314984 | IC_kwDOAMm_X85Hi1po | 1217238 | 2022-07-30T23:55:04Z | 2022-07-30T23:55:04Z | MEMBER |
Yes, I'm pretty sure "float" means single precision (np.float32), given that "double" certainly means double precision (no.float64).
Yes, I believe so.
I think we can treat this a bug fix and just go forward with it. Yes, some people are going to be surprised, but I don't think it's distruptive enough that we need to go to a major effort to preserve backwards compatibility. It should already be straightforward to work around by setting |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
343659822 |