issue_comments: 328399848
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/1566#issuecomment-328399848 | https://api.github.com/repos/pydata/xarray/issues/1566 | 328399848 | MDEyOklzc3VlQ29tbWVudDMyODM5OTg0OA== | 1217238 | 2017-09-11T02:30:07Z | 2017-09-11T02:30:07Z | MEMBER | Thanks for raising this concern. I think we have been gradually improving the quality of our error messages, but I agree that we still have a large opportunity for improvement. This also one area where someone inexperienced can have a big impact. Experienced developers are likely to gloss over confusing error messages (or not see them at all) because they already understand what's going on. Any GitHub issues you open when you encounter an error that was not as helpful as possible would be gratefully appreciated. I've been trying to collect these under the Our contributing guidelines (see https://github.com/pydata/xarray/pull/1485) should make it clear that full code to reproduce is not required for such cases. Potentially it would also make sense to audit some of our code line by line to check that error messages are as good as possible. cc @jhamman |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
256557897 |