issue_comments
4 rows where issue = 256251595 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- 0.8.2 incompatible with pandas 0.20.1 ? · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
328234900 | https://github.com/pydata/xarray/issues/1563#issuecomment-328234900 | https://api.github.com/repos/pydata/xarray/issues/1563 | MDEyOklzc3VlQ29tbWVudDMyODIzNDkwMA== | fmaussion 10050469 | 2017-09-08T23:15:36Z | 2017-09-08T23:15:36Z | MEMBER | To address your pickle issue you might consider one of the other serialization options for xarray data structures, for example NetCDF: http://xarray.pydata.org/en/stable/io.html#netcdf |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
0.8.2 incompatible with pandas 0.20.1 ? 256251595 | |
328205461 | https://github.com/pydata/xarray/issues/1563#issuecomment-328205461 | https://api.github.com/repos/pydata/xarray/issues/1563 | MDEyOklzc3VlQ29tbWVudDMyODIwNTQ2MQ== | fmaussion 10050469 | 2017-09-08T20:26:20Z | 2017-09-08T20:26:20Z | MEMBER | xarray's development is independent from pandas', and at the time xarray v0.8.2 was released (2016), nobody could predict what going to happen with pandas in 2017. So yes, if you need to stick to v0.8.2, strict version requirement is the only way to go. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
0.8.2 incompatible with pandas 0.20.1 ? 256251595 | |
328168623 | https://github.com/pydata/xarray/issues/1563#issuecomment-328168623 | https://api.github.com/repos/pydata/xarray/issues/1563 | MDEyOklzc3VlQ29tbWVudDMyODE2ODYyMw== | kefirbandi 1277781 | 2017-09-08T17:41:05Z | 2017-09-08T17:41:05Z | CONTRIBUTOR | Actually I just saw that the requirement for xarray 0.8.2 is: pandas >= 0.15.0, I don't know whether it is possible to specify: 0.19.1>=pandas>=0.15.0. Just ran into this issue when wanted to install packages for some newcomers in our company. But actually we solved the issue by adding strict version requirement for both xarray and pandas. (We need these versions because we have some pickled files using these formats which we need to read. Until I find the time to get rid of them.) |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
0.8.2 incompatible with pandas 0.20.1 ? 256251595 | |
328102245 | https://github.com/pydata/xarray/issues/1563#issuecomment-328102245 | https://api.github.com/repos/pydata/xarray/issues/1563 | MDEyOklzc3VlQ29tbWVudDMyODEwMjI0NQ== | fmaussion 10050469 | 2017-09-08T13:24:18Z | 2017-09-08T13:24:18Z | MEMBER | xarray V0.8.2 was released on Aug 19, 2016 and pandas v0.20.1 on May 5, 2017 Any reason why you need to stick to 0.8.2? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
0.8.2 incompatible with pandas 0.20.1 ? 256251595 |
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 2