issue_comments: 238745229
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/957#issuecomment-238745229 | https://api.github.com/repos/pydata/xarray/issues/957 | 238745229 | MDEyOklzc3VlQ29tbWVudDIzODc0NTIyOQ== | 1217238 | 2016-08-10T01:56:22Z | 2016-08-10T01:56:22Z | MEMBER | I would be interested to know if registering an accessor works for you, which was designed for exactly this sort of use case: http://xarray.pydata.org/en/stable/internals.html#extending-xarray The reason why I chose not to just use the qualified name is that But I'd be happy to use qualified names for subclasses not builtin to xarray. Currently you can find this logic in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
170305429 |