issue_comments

Table actions

2 rows where issue = 282178751 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

  • Add compute=False keywords to `to_foo` functions · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
367806166 https://github.com/pydata/xarray/issues/1784#issuecomment-367806166 https://api.github.com/repos/pydata/xarray/issues/1784 MDEyOklzc3VlQ29tbWVudDM2NzgwNjE2Ng== shoyer 1217238 2018-02-22T20:08:46Z 2018-02-22T20:08:46Z MEMBER

sync=False is a private, undocumented API. I think it's only found on the internal to_netcdf function in xarray.backends.api, not the to_netcdf method.

Currently, to_netcdf() will either return: - None if a path or file-like object was passed to to_netcdf(). - bytes representing the file's data if no path or file was provided.

In either case I think it could make sense to optionally replace the return value with a dask delayed object, which in turn evaluates to either None or bytes when computed.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add compute=False keywords to `to_foo` functions 282178751
351785902 https://github.com/pydata/xarray/issues/1784#issuecomment-351785902 https://api.github.com/repos/pydata/xarray/issues/1784 MDEyOklzc3VlQ29tbWVudDM1MTc4NTkwMg== shoyer 1217238 2017-12-14T17:48:48Z 2017-12-14T17:48:48Z MEMBER

Yes, this sounds like a natural improvement to me!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add compute=False keywords to `to_foo` functions 282178751

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