issue_comments
8 rows where issue = 278453914 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Is there a reason for why DataArray.swap_dims() cannot be done in place like Dataset.swap_dims? · 8 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
348716669 | https://github.com/pydata/xarray/issues/1755#issuecomment-348716669 | https://api.github.com/repos/pydata/xarray/issues/1755 | MDEyOklzc3VlQ29tbWVudDM0ODcxNjY2OQ== | shoyer 1217238 | 2017-12-02T20:09:17Z | 2017-12-02T20:09:17Z | MEMBER |
Yes, this is a good idea! Opened #1756 to keep track. |
{ "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 | |
348682403 | https://github.com/pydata/xarray/issues/1755#issuecomment-348682403 | https://api.github.com/repos/pydata/xarray/issues/1755 | MDEyOklzc3VlQ29tbWVudDM0ODY4MjQwMw== | fmaussion 10050469 | 2017-12-02T10:18:28Z | 2017-12-02T10:18:28Z | MEMBER |
How about deprecating these? Would that be too much of a change you think? (I never use them) |
{ "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 | |
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 | |
348554537 | https://github.com/pydata/xarray/issues/1755#issuecomment-348554537 | https://api.github.com/repos/pydata/xarray/issues/1755 | MDEyOklzc3VlQ29tbWVudDM0ODU1NDUzNw== | shoyer 1217238 | 2017-12-01T17:19:53Z | 2017-12-01T17:19:53Z | MEMBER | If I did it again, I would remove the Why not make your accessor method return a new DataArray object? That would be more inline with how most xarray methods work. If you have any special attributes you've set on the accessor you can copy those over to the new result. |
{ "total_count": 2, "+1": 2, "-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.
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 | |
348504868 | https://github.com/pydata/xarray/issues/1755#issuecomment-348504868 | https://api.github.com/repos/pydata/xarray/issues/1755 | MDEyOklzc3VlQ29tbWVudDM0ODUwNDg2OA== | rabernat 1197350 | 2017-12-01T14:14:25Z | 2017-12-01T14:14:25Z | MEMBER | Ah right. So you would do
|
{ "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 | |
348491227 | https://github.com/pydata/xarray/issues/1755#issuecomment-348491227 | https://api.github.com/repos/pydata/xarray/issues/1755 | MDEyOklzc3VlQ29tbWVudDM0ODQ5MTIyNw== | rabernat 1197350 | 2017-12-01T13:12:24Z | 2017-12-01T13:12:24Z | MEMBER | swap_dims is not an in-place operation http://xarray.pydata.org/en/stable/generated/xarray.Dataset.swap_dims.html It returns a new dataset with swapped dims. If you want to do it in place, there is a keyword argument for that. Sent from my iPhone
|
{ "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 |
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 4