issue_comments: 409829431
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/2292#issuecomment-409829431 | https://api.github.com/repos/pydata/xarray/issues/2292 | 409829431 | MDEyOklzc3VlQ29tbWVudDQwOTgyOTQzMQ== | 1217238 | 2018-08-02T07:12:17Z | 2018-08-02T07:12:17Z | MEMBER | Most of the places in the code where we do the That said, checking explicitly for strings wasn't take a careful API choice. I could see a case for replacing all these "as sequence" casts with something more generic, e.g., based on checking explicitly for more generic scalar types. Certainly enums should be scalars. If possible, I would rather stick to duck typing for any requirements we put on names. Base classes don't feel terribly Pythonic. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
341643235 |