issue_comments: 236736739
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/929#issuecomment-236736739 | https://api.github.com/repos/pydata/xarray/issues/929 | 236736739 | MDEyOklzc3VlQ29tbWVudDIzNjczNjczOQ== | 1217238 | 2016-08-01T23:15:28Z | 2016-08-01T23:15:28Z | MEMBER | This difference is certainly intentional. You're right that we currently don't explicitly state how we handle lists or numpy arrays in the docs -- that should be fixed. At one point, we did have heuristics that did this sort of fallback logic (allowing lists, and checking the length of the tuple/list). But we eventually removed these checks, because this sort of value dependent behavior makes code difficult to predict. At least now it always behaves consistently when given a list or a tuple. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
168754274 |