issue_comments
7 rows where issue = 344093951 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- DOC: add initial draft of a development roadmap for xarray · 7 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
409997671 | https://github.com/pydata/xarray/pull/2309#issuecomment-409997671 | https://api.github.com/repos/pydata/xarray/issues/2309 | MDEyOklzc3VlQ29tbWVudDQwOTk5NzY3MQ== | dcherian 2448579 | 2018-08-02T17:01:36Z | 2018-08-02T17:01:36Z | MEMBER | @aseyboldt Thanks! Please file issues for any feature requests you might have. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DOC: add initial draft of a development roadmap for xarray 344093951 | |
409992634 | https://github.com/pydata/xarray/pull/2309#issuecomment-409992634 | https://api.github.com/repos/pydata/xarray/issues/2309 | MDEyOklzc3VlQ29tbWVudDQwOTk5MjYzNA== | aseyboldt 1882397 | 2018-08-02T16:45:44Z | 2018-08-02T16:45:44Z | NONE | I noticed and appreciate those plotting additions :-) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DOC: add initial draft of a development roadmap for xarray 344093951 | |
409976901 | https://github.com/pydata/xarray/pull/2309#issuecomment-409976901 | https://api.github.com/repos/pydata/xarray/issues/2309 | MDEyOklzc3VlQ29tbWVudDQwOTk3NjkwMQ== | shoyer 1217238 | 2018-08-02T15:56:06Z | 2018-08-02T15:56:06Z | MEMBER | Thanks for the feedback! @dcherian and @yohai have been making some nice improvements to plotting recently. It seems like each release has a few new features. Fortunately plotting goes in the category of "straightforward to improve without a major refactoring", which is probably why we didn't put it on the roadmap! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DOC: add initial draft of a development roadmap for xarray 344093951 | |
409828598 | https://github.com/pydata/xarray/pull/2309#issuecomment-409828598 | https://api.github.com/repos/pydata/xarray/issues/2309 | MDEyOklzc3VlQ29tbWVudDQwOTgyODU5OA== | aseyboldt 1882397 | 2018-08-02T07:08:27Z | 2018-08-02T07:08:27Z | NONE | This roadmap sounds great! We plan on using xarray to store all traces in pymc4. The biggest item on my wish list for that is better support for plotting. I regularly convert traces to pandas and use the plotting functions there, or I convert it so that I can use seaborn. Better support for hierarchical indexes sounds useful as well. They can be a bit surprising right now, and they can't be serialised to netCDF. The documentation is quite important our use case. As it is, we are asking our users to learn Bayesian stats, diagnosing sampler issues and possibly some theano or tensorflow. When we switch to xarray, our users have to learn the basics of that as well. Most won't even have heard about netCDF. One thing in particular that I noticed is that many people seem to get confused about the difference between coordinates and dimensions at some point. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DOC: add initial draft of a development roadmap for xarray 344093951 | |
408565221 | https://github.com/pydata/xarray/pull/2309#issuecomment-408565221 | https://api.github.com/repos/pydata/xarray/issues/2309 | MDEyOklzc3VlQ29tbWVudDQwODU2NTIyMQ== | shoyer 1217238 | 2018-07-27T23:50:23Z | 2018-07-27T23:50:23Z | MEMBER | Here are the responses on Twitter: https://twitter.com/shoyer/status/1021788358048010240 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DOC: add initial draft of a development roadmap for xarray 344093951 | |
408564776 | https://github.com/pydata/xarray/pull/2309#issuecomment-408564776 | https://api.github.com/repos/pydata/xarray/issues/2309 | MDEyOklzc3VlQ29tbWVudDQwODU2NDc3Ng== | jhamman 2443309 | 2018-07-27T23:45:58Z | 2018-07-27T23:45:58Z | MEMBER | I think we merge this to make it more visible. @fmaussion - we got a few comments asking if/how the core changes proposed in xarray would make using the library more difficult. Those worries seemed to be easily put to rest. Beyond that, things seemed mostly positive/quite. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DOC: add initial draft of a development roadmap for xarray 344093951 | |
408348531 | https://github.com/pydata/xarray/pull/2309#issuecomment-408348531 | https://api.github.com/repos/pydata/xarray/issues/2309 | MDEyOklzc3VlQ29tbWVudDQwODM0ODUzMQ== | fmaussion 10050469 | 2018-07-27T08:22:17Z | 2018-07-27T08:22:17Z | MEMBER | Any comment/suggestion from the larger xarray community? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
DOC: add initial draft of a development roadmap for xarray 344093951 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 5