issue_comments: 523833526
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/1097#issuecomment-523833526 | https://api.github.com/repos/pydata/xarray/issues/1097 | 523833526 | MDEyOklzc3VlQ29tbWVudDUyMzgzMzUyNg== | 6213168 | 2019-08-22T09:49:00Z | 2019-08-22T09:49:00Z | MEMBER | The biggest problem is with all the Dataset methods and accessors that return a DataArray, and vice versa. Anybody who wants to create a coupled pair of Dataset and DataArray subclasses will need to hunt down all methods and accessors that return the other class in the pair and override them. May I ask what are the practical use cases for subclassing? In several years worth of day-to-day use of xarray I always found that encapsulation felt much more natural. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
188113943 |