issue_comments

Table actions

4 rows where user = 25015426 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • leeviannala · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
348682194 https://github.com/pydata/xarray/issues/1755#issuecomment-348682194 https://api.github.com/repos/pydata/xarray/issues/1755 MDEyOklzc3VlQ29tbWVudDM0ODY4MjE5NA== leeviannala 25015426 2017-12-02T10:13:39Z 2017-12-02T10:13:39Z CONTRIBUTOR

Thank you for your explination. I will to look into my problem from another angle.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Is there a reason for why DataArray.swap_dims() cannot be done in place like Dataset.swap_dims? 278453914
348536836 https://github.com/pydata/xarray/issues/1755#issuecomment-348536836 https://api.github.com/repos/pydata/xarray/issues/1755 MDEyOklzc3VlQ29tbWVudDM0ODUzNjgzNg== leeviannala 25015426 2017-12-01T16:14:43Z 2017-12-01T16:14:43Z CONTRIBUTOR

Seems like I forgot a confusing line in my example. For example in dataarray_accessor, we have a need for in-place swap. python cube = xr.DataArray(arr, dims=['ya', 'x', 'y'], coords={'y':[1,3], 'ya':[1,2,3,6], 'x':[1,2,5]}) #First dataarray object. cube now referes to this. cube.coords['x2'] = ('x', [1,2,3]) cube = cube.swap_dims({'x':'x2'}) #Second dataarray object. cube now refers to this and first dataarray object is now forgotten vs: python cube = xr.DataArray(arr, dims=['ya', 'x', 'y'], coords={'y':[1,3], 'ya':[1,2,3,6], 'x':[1,2,5]}) #First dataarray object. cube now referes to this. cube.coords['x2'] = ('x', [1,2,3]) cube.swap_dims({'x':'x2'}, inline=True) #This just changes the first dataarray object. cube still refers to the first dataarray object

So the question again was, is there a reason, why the inline keyword is implemented on dataset, but not on dataarray.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Is there a reason for why DataArray.swap_dims() cannot be done in place like Dataset.swap_dims? 278453914
348492848 https://github.com/pydata/xarray/issues/1755#issuecomment-348492848 https://api.github.com/repos/pydata/xarray/issues/1755 MDEyOklzc3VlQ29tbWVudDM0ODQ5Mjg0OA== leeviannala 25015426 2017-12-01T13:20:07Z 2017-12-01T13:20:07Z CONTRIBUTOR

@rabernat, please note that i'm working with dataarrays. There is no inplace keyword.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Is there a reason for why DataArray.swap_dims() cannot be done in place like Dataset.swap_dims? 278453914
325572050 https://github.com/pydata/xarray/pull/1526#issuecomment-325572050 https://api.github.com/repos/pydata/xarray/issues/1526 MDEyOklzc3VlQ29tbWVudDMyNTU3MjA1MA== leeviannala 25015426 2017-08-29T06:53:20Z 2017-08-29T06:53:20Z CONTRIBUTOR

I'm getting random errors on flake8 test from whats-new.rst, but otherwise it passes.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Fixed issue #1520, by adding a if-else that checks for None 252813229

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