issue_comments: 226249845
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/742#issuecomment-226249845 | https://api.github.com/repos/pydata/xarray/issues/742 | 226249845 | MDEyOklzc3VlQ29tbWVudDIyNjI0OTg0NQ== | 1217238 | 2016-06-15T16:54:45Z | 2016-06-15T16:54:45Z | MEMBER | I think this could make it into merge, which I am in the process of refactoring in https://github.com/pydata/xarray/pull/857. The key difference from @jcmgray's implementation that I would want is a check to make sure that the data is all on different domains when using @JamesPHoughton I agree with @jcmgray that the dtype=object is what you should expect here. It's hard to create fixed length strings in xarray/pandas because that precludes the possibility of missing values, so we tend to convert strings to object dtype when merged/concatenated. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
130753818 |