issue_comments
4 rows where issue = 193226503 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- "ncdump -h" like repr? · 4 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 265178944 | https://github.com/pydata/xarray/issues/1150#issuecomment-265178944 | https://api.github.com/repos/pydata/xarray/issues/1150 | MDEyOklzc3VlQ29tbWVudDI2NTE3ODk0NA== | fmaussion 10050469 | 2016-12-06T15:27:47Z | 2016-12-06T15:27:47Z | MEMBER | Another idea would be to simply add the variables attrs to the current I'm getting slightly off-topic, but I am also in favor or removing the data values from the repr altogether, as it creates problems and is not really useful (I think). See also: https://github.com/pydata/xarray/issues/1044 https://github.com/pydata/xarray/issues/820 and other issues mentioning repr : https://github.com/pydata/xarray/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20repr |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
"ncdump -h" like repr? 193226503 | |
| 265168933 | https://github.com/pydata/xarray/issues/1150#issuecomment-265168933 | https://api.github.com/repos/pydata/xarray/issues/1150 | MDEyOklzc3VlQ29tbWVudDI2NTE2ODkzMw== | shoyer 1217238 | 2016-12-06T14:51:20Z | 2016-12-06T14:51:20Z | MEMBER | pandas already has a (rarely used) In [4]: df Out[4]: x y z 0 1 a -1 1 2 b -2 2 3 c -3 In [5]: df.info()
<class 'pandas.core.frame.DataFrame'>
RangeIndex: 3 entries, 0 to 2
Data columns (total 3 columns):
x 3 non-null int64
y 3 non-null object
z 3 non-null int64
dtypes: int64(2), object(1)
memory usage: 152.0+ bytes
I might pick a name that including a specific reference to attributes for this, maybe |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
"ncdump -h" like repr? 193226503 | |
| 264963094 | https://github.com/pydata/xarray/issues/1150#issuecomment-264963094 | https://api.github.com/repos/pydata/xarray/issues/1150 | MDEyOklzc3VlQ29tbWVudDI2NDk2MzA5NA== | jhamman 2443309 | 2016-12-05T20:11:09Z | 2016-12-05T20:11:09Z | MEMBER | I think something like this would be quite useful. This is most applicable to the
|
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
"ncdump -h" like repr? 193226503 | |
| 264646057 | https://github.com/pydata/xarray/issues/1150#issuecomment-264646057 | https://api.github.com/repos/pydata/xarray/issues/1150 | MDEyOklzc3VlQ29tbWVudDI2NDY0NjA1Nw== | shoyer 1217238 | 2016-12-03T15:36:02Z | 2016-12-03T15:36:02Z | MEMBER | I don't think anything like this currently exists. I agree that some way to conveniently summarize attributes would be nice to have. See also #244. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
"ncdump -h" like repr? 193226503 |
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 3