issue_comments: 596632059
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/3851#issuecomment-596632059 | https://api.github.com/repos/pydata/xarray/issues/3851 | 596632059 | MDEyOklzc3VlQ29tbWVudDU5NjYzMjA1OQ== | 1197350 | 2020-03-09T16:24:35Z | 2020-03-09T16:24:35Z | MEMBER | Shouldn't this be solved by the entry points refactor of the backends? In the future, I imagine that the zarr backend for xarray will not live in xarray but rather in some third-party package. That package could expose all of these functions as public API. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
578017585 |