html_url,issue_url,id,node_id,user,created_at,updated_at,author_association,body,reactions,performed_via_github_app,issue
https://github.com/pydata/xarray/issues/3552#issuecomment-556111055,https://api.github.com/repos/pydata/xarray/issues/3552,556111055,MDEyOklzc3VlQ29tbWVudDU1NjExMTA1NQ==,4179064,2019-11-20T17:05:33Z,2019-11-20T17:05:33Z,NONE,"Ah, thanks very much! I'll switch to using that syntax instead.","{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,525903846
https://github.com/pydata/xarray/issues/3552#issuecomment-556096924,https://api.github.com/repos/pydata/xarray/issues/3552,556096924,MDEyOklzc3VlQ29tbWVudDU1NjA5NjkyNA==,4179064,2019-11-20T16:53:40Z,2019-11-20T16:53:40Z,NONE,I apologize for this slight tangent but it's related to why we use sets in `drop()`. Is there a good way in xarray to only *keep* a list of variables? Our approach is to create a set of all variable and subtract from it a set of variables we want to keep and to drop the resulting set of variables we *don't* want to keep. But it's hard for me to imagine others don't also need this functionality.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,525903846
https://github.com/pydata/xarray/issues/3552#issuecomment-556095452,https://api.github.com/repos/pydata/xarray/issues/3552,556095452,MDEyOklzc3VlQ29tbWVudDU1NjA5NTQ1Mg==,4179064,2019-11-20T16:50:15Z,2019-11-20T16:50:15Z,NONE,"> Additionally, I think we have a documentation bug: I can't reach the documentation on drop.
Yes, I noticed that, too. I assumed it wasn't being documented anymore because it was considered deprecated. ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,525903846
https://github.com/pydata/xarray/issues/3552#issuecomment-556091171,https://api.github.com/repos/pydata/xarray/issues/3552,556091171,MDEyOklzc3VlQ29tbWVudDU1NjA5MTE3MQ==,4179064,2019-11-20T16:41:09Z,2019-11-20T16:43:01Z,NONE,"> @dcherian - are you suggesting that @xylar change his downstream code to use drop_vars instead? drop_vars has been deprecated. I don't think that's the right response here.
I'm confused. In 0.14.1, `drop_vars` seems to have just been introduced and `drop` seems to have been dropped.
> How about drop_vars instead?
Yes, I switched to `drop_vars` but first I had to make a new build of my conda package that constrains the dependency `xarray <0.14.0` because it's broken with 0.14.1. So that's why I'm concerned. I have to do a new release before this fix propagates to my users.
So @rabernat and @dcherian, please clarify if I should be switching to `drop_vars` or if I am going to run into issues yet again if I do so?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,525903846
https://github.com/pydata/xarray/issues/3552#issuecomment-556077504,https://api.github.com/repos/pydata/xarray/issues/3552,556077504,MDEyOklzc3VlQ29tbWVudDU1NjA3NzUwNA==,4179064,2019-11-20T16:10:54Z,2019-11-20T16:11:13Z,NONE,"I believe a `set()` object should be a valid `labels` argument according to the documentation of `drop()`:
http://xarray.pydata.org/en/v0.14.0/generated/xarray.Dataset.drop.html#xarray.Dataset.drop","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,525903846
https://github.com/pydata/xarray/issues/2680#issuecomment-454522920,https://api.github.com/repos/pydata/xarray/issues/2680,454522920,MDEyOklzc3VlQ29tbWVudDQ1NDUyMjkyMA==,4179064,2019-01-15T19:38:04Z,2019-01-15T19:38:04Z,NONE,"I think this might be a dask/numpy issue and probably unrelated to xarray: https://github.com/dask/dask/issues/4378
I'll close this but others can re-open if need be.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,399457300
https://github.com/pydata/xarray/issues/2636#issuecomment-450455452,https://api.github.com/repos/pydata/xarray/issues/2636,450455452,MDEyOklzc3VlQ29tbWVudDQ1MDQ1NTQ1Mg==,4179064,2018-12-29T02:07:54Z,2018-12-29T02:07:54Z,NONE,"@zxdawn, I was able to verify that, by adding `decode_times=False` to your code, I get:
```
keys of merge:
odict_keys(['lon', 'lat', 'temperature', 'time'])
time of merge:
int64 time(time)
units: hours since 2015-01-01
unlimited dimensions:
current shape = (6,)
filling on, default _FillValue of -9223372036854775806 used
```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,394625579
https://github.com/pydata/xarray/issues/2636#issuecomment-450400275,https://api.github.com/repos/pydata/xarray/issues/2636,450400275,MDEyOklzc3VlQ29tbWVudDQ1MDQwMDI3NQ==,4179064,2018-12-28T17:54:19Z,2018-12-28T17:54:19Z,NONE,"Depending on your needs, you might be able to get away with calling `open_mfdataset` with `decode_times=False`. This should leave your `time` coordinate as it is (i.e. integer hours since 2015-01-01) but that will limit the types of operations you can do on the `time` dimension because it will not be converted to some kind of `DateTime` object. For example, it would be difficult to do time averaging that is aware of months, years, etc.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,394625579
https://github.com/pydata/xarray/issues/2064#issuecomment-381993716,https://api.github.com/repos/pydata/xarray/issues/2064,381993716,MDEyOklzc3VlQ29tbWVudDM4MTk5MzcxNg==,4179064,2018-04-17T13:33:05Z,2018-04-17T13:33:05Z,NONE,"Hmm, I agree that it shouldn't be hard but I don't really have time to do this right now. If no one has had a chance to look into it by mid May I might be able to take it on then.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381731078,https://api.github.com/repos/pydata/xarray/issues/2064,381731078,MDEyOklzc3VlQ29tbWVudDM4MTczMTA3OA==,4179064,2018-04-16T20:02:53Z,2018-04-16T20:02:53Z,NONE,"@rabernat, your suggestion above has worked perfectly to get our unit tests working again in [MPAS-Analysis](https://github.com/MPAS-Dev/MPAS-Analysis) so that will tide us over until this issue can be addressed directly in xarray. Thanks!","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381730268,https://api.github.com/repos/pydata/xarray/issues/2064,381730268,MDEyOklzc3VlQ29tbWVudDM4MTczMDI2OA==,4179064,2018-04-16T20:00:14Z,2018-04-16T20:00:14Z,NONE,"Yes, I think that's exactly right.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381723442,https://api.github.com/repos/pydata/xarray/issues/2064,381723442,MDEyOklzc3VlQ29tbWVudDM4MTcyMzQ0Mg==,4179064,2018-04-16T19:37:02Z,2018-04-16T19:37:02Z,NONE,"Yes, true. I'm trying to think if there are any examples where the fixed-in-time variables would not be coordinates. So far, none come to mind. Thanks for the tip.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381722358,https://api.github.com/repos/pydata/xarray/issues/2064,381722358,MDEyOklzc3VlQ29tbWVudDM4MTcyMjM1OA==,4179064,2018-04-16T19:33:09Z,2018-04-16T19:33:09Z,NONE,"@rabernat, so you're fooling xarray into not including the `time` dimension in your non-time variables by making them coordinates in the above example?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381718089,https://api.github.com/repos/pydata/xarray/issues/2064,381718089,MDEyOklzc3VlQ29tbWVudDM4MTcxODA4OQ==,4179064,2018-04-16T19:17:31Z,2018-04-16T19:18:17Z,NONE,"@shoyer, I stand corrected. in 0.10.1, I also see the `Time` variable getting added to `refBottomDepth` when I open multiple files. So maybe this is not in fact a new problem but an existing issue that happened to behave as I expected *only* when opening a single file in previous versions. Sorry for not noticing that sooner.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381717309,https://api.github.com/repos/pydata/xarray/issues/2064,381717309,MDEyOklzc3VlQ29tbWVudDM4MTcxNzMwOQ==,4179064,2018-04-16T19:14:39Z,2018-04-16T19:14:39Z,NONE,"@shoyer, in that case as well, `Time` is added to `refBottomDepth` in v 0.10.3, which was not the case in previous xarray versions.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258
https://github.com/pydata/xarray/issues/2064#issuecomment-381700098,https://api.github.com/repos/pydata/xarray/issues/2064,381700098,MDEyOklzc3VlQ29tbWVudDM4MTcwMDA5OA==,4179064,2018-04-16T18:16:47Z,2018-04-16T18:16:47Z,NONE,cc @pwolfram ,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,314764258