issue_comments
4 rows where author_association = "MEMBER", issue = 290593053 and user = 1217238 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- xarray contrib module · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
483336107 | https://github.com/pydata/xarray/issues/1850#issuecomment-483336107 | https://api.github.com/repos/pydata/xarray/issues/1850 | MDEyOklzc3VlQ29tbWVudDQ4MzMzNjEwNw== | shoyer 1217238 | 2019-04-15T17:03:27Z | 2019-04-15T17:03:27Z | MEMBER | @teoliphant thanks for sharing your thoughts! I would be very happy to collaborate on what a protocol for labeled arrays in Python could look like. Xarray is one useful implementations of labeled arrays, but it's definitely not the only one. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray contrib module 290593053 | |
483333879 | https://github.com/pydata/xarray/issues/1850#issuecomment-483333879 | https://api.github.com/repos/pydata/xarray/issues/1850 | MDEyOklzc3VlQ29tbWVudDQ4MzMzMzg3OQ== | shoyer 1217238 | 2019-04-15T16:57:08Z | 2019-04-15T16:57:08Z | MEMBER | For what it's worth, TensorFlow has decided that bundling contrib modules into TensorFlow as |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray contrib module 290593053 | |
368201831 | https://github.com/pydata/xarray/issues/1850#issuecomment-368201831 | https://api.github.com/repos/pydata/xarray/issues/1850 | MDEyOklzc3VlQ29tbWVudDM2ODIwMTgzMQ== | shoyer 1217238 | 2018-02-24T05:30:01Z | 2018-02-24T05:30:01Z | MEMBER | Personally I'd rather have "awesome xarray" listed somewhere prominently in the xarray docs, along with mentions inline in the docs anywhere where they are particularly relevant . The very short list that is currently there is based upon a handful of projects that I knew about a few years ago, but it's definitely woefully out of date now. On Fri, Feb 23, 2018 at 9:23 PM Noah D Brenowitz notifications@github.com wrote:
|
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray contrib module 290593053 | |
359959683 | https://github.com/pydata/xarray/issues/1850#issuecomment-359959683 | https://api.github.com/repos/pydata/xarray/issues/1850 | MDEyOklzc3VlQ29tbWVudDM1OTk1OTY4Mw== | shoyer 1217238 | 2018-01-23T22:54:51Z | 2018-01-23T22:54:51Z | MEMBER | I think domain specific dependencies are a pretty decisive argument in favor of the separate repository model. TensorFlow doesn't relax its code quality standards for contrib packages -- it's more about reducing guarantees of API stability or maintenance. That works OK for TensorFlow in part because the authors of most contrib packages are Google software engineers. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
xarray contrib module 290593053 |
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 1