issue_comments
3 rows where user = 19690642 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- MuellerSeb · 3 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1514362199 | https://github.com/pydata/xarray/issues/7765#issuecomment-1514362199 | https://api.github.com/repos/pydata/xarray/issues/7765 | IC_kwDOAMm_X85aQ1VX | MuellerSeb 19690642 | 2023-04-19T08:47:08Z | 2023-04-19T08:47:08Z | NONE | Pandas seems to also look at the policies of its dependencies like Numpy: https://numpy.org/neps/nep-0029-deprecation_policy.html#support-table |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Revisiting Xarray's Minimum dependency versions policy 1673579421 | |
1514353030 | https://github.com/pydata/xarray/issues/7765#issuecomment-1514353030 | https://api.github.com/repos/pydata/xarray/issues/7765 | IC_kwDOAMm_X85aQzGG | MuellerSeb 19690642 | 2023-04-19T08:40:02Z | 2023-04-19T08:40:02Z | NONE | What about dependencies like pandas? Maybe it could be a good idea to synchronize policies to avoid conflicts there. As written before, xarray is currently broken when installing it with I now need to add this to the dependency list of my packages depending on xarray:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Revisiting Xarray's Minimum dependency versions policy 1673579421 | |
1513228411 | https://github.com/pydata/xarray/pull/7461#issuecomment-1513228411 | https://api.github.com/repos/pydata/xarray/issues/7461 | IC_kwDOAMm_X85aMgh7 | MuellerSeb 19690642 | 2023-04-18T14:08:36Z | 2023-04-18T14:08:36Z | NONE | This also breaks xarray on ubuntu 20.04 which ships with Python 3.8 and is supported until April 2025. Python 3.8 is also supported at least until October 2024. Together with the Pandas 2 issue (that I am also running into), this is very unfortunate. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
bump minimum versions, drop py38 1550109629 |
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]);
issue 2