issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 988158051 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • shoyer · 2 ✖

issue 1

  • Implement __sizeof__ on objects? · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
933822350 https://github.com/pydata/xarray/issues/5764#issuecomment-933822350 https://api.github.com/repos/pydata/xarray/issues/5764 IC_kwDOAMm_X843qP-O shoyer 1217238 2021-10-04T20:16:48Z 2021-10-04T20:16:48Z MEMBER

I don't love going against the guidance from Python core developers. My gut is that a Dask-specific protocol may be safer. That said, if Dask is the only library using sys.getsizeof() for some real purpose, then perhaps this is safe enough.

There's still some ambiguity to me about exactly what should be included in "size of" (e.g., do we include lazy values or not?) but we can probably figure that out. I suspect Xarray's implementation would be need to be recursive in some way, to handle nested Dask or lazy arrays.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implement __sizeof__ on objects? 988158051
914051097 https://github.com/pydata/xarray/issues/5764#issuecomment-914051097 https://api.github.com/repos/pydata/xarray/issues/5764 IC_kwDOAMm_X842e1AZ shoyer 1217238 2021-09-07T07:12:07Z 2021-09-07T07:12:07Z MEMBER

It seems like the concensus from https://bugs.python.org/issue15436 is that only C extension types should implement __sizeof__.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Implement __sizeof__ on objects? 988158051

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);