issue_comments
2 rows where issue = 1462173557 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Support for python 3.11 · 2 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1336346524 | https://github.com/pydata/xarray/issues/7316#issuecomment-1336346524 | https://api.github.com/repos/pydata/xarray/issues/7316 | IC_kwDOAMm_X85Ppwec | sxwebster 57381773 | 2022-12-04T08:12:36Z | 2022-12-04T08:12:36Z | NONE | @dcherian Numba is looking at having a Python 3.11 RC ready by end of year, hopefully. It would be lovely to see Numba + Xarray catch up as 3.11 (and 3.12) look to have some big speed improvements. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Support for python 3.11 1462173557 | |
| 1329371101 | https://github.com/pydata/xarray/issues/7316#issuecomment-1329371101 | https://api.github.com/repos/pydata/xarray/issues/7316 | IC_kwDOAMm_X85PPJfd | dcherian 2448579 | 2022-11-28T16:18:49Z | 2022-11-28T16:18:49Z | MEMBER | Usually the full test env is limited by numba. I think for 3.10 we created a new test workflow without numba. So that could be a good way to go. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Support for python 3.11 1462173557 |
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