issue_comments: 463829789
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/pull/2766#issuecomment-463829789 | https://api.github.com/repos/pydata/xarray/issues/2766 | 463829789 | MDEyOklzc3VlQ29tbWVudDQ2MzgyOTc4OQ== | 1217238 | 2019-02-14T22:34:04Z | 2019-02-14T22:34:04Z | MEMBER | It's not entirely clear to me where we should draw the line between included wrappers in xarray and leaving this to external packages, e.g., see xr-scipy.readthedocs.io If we do include this in xarray, I would prefer to have both (1) a clear policy around what we include (e.g., only direct wrappers for numpy/scipy functions) and (2) a separate namespace for wrapped functions, e.g., Note that with NEP-18 we'll be able to directly everything in numpy.linalg on xarray objects, without requiring the use of a separate wrapper. cc @pydata/xarray for discussion |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
409618015 |