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/pull/3417#issuecomment-1109755369,https://api.github.com/repos/pydata/xarray/issues/3417,1109755369,IC_kwDOAMm_X85CJYXp,2444231,2022-04-26T12:49:13Z,2022-04-26T12:49:13Z,NONE,"Any progress on this one? I would like to use this functionality. I have a workaround for right now, but it would be nice to do it ""correctly""","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,509421390
https://github.com/pydata/xarray/pull/3858#issuecomment-598569859,https://api.github.com/repos/pydata/xarray/issues/3858,598569859,MDEyOklzc3VlQ29tbWVudDU5ODU2OTg1OQ==,2444231,2020-03-13T06:21:35Z,2020-03-13T06:25:43Z,NONE,"Yes, I agree. Having a library only depend on the environment is less than optimal to say the least. The main reason behind this was to allow one of the GRB backends to read custom tables. I've already contacted both the cfgrib and PyNIO people to see about changing this to something more flexible.
Regarding writing my own utility: I'm afraid this introduces one more hoop for end users to jump through. If I can tell my colleagues ""Hey just use Xarray"", that normally works pretty well. If I now need to say ""Hey, use my own little thing plus Xarray plus ...."" (who knows what else) might introduce more friction.
However, it's an interesting idea: How challenging would it be to write my own Xarray backend (In this case for GRB files) and include that instead? Would Xarray be open to including a further backend? That would separate the logic into it's own project and if anything breaks, then the Xarray team would have less to worry about and can just refer issues to the backend development team (so, I guess me 😉)...","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,579722569
https://github.com/pydata/xarray/issues/3853#issuecomment-598035459,https://api.github.com/repos/pydata/xarray/issues/3853,598035459,MDEyOklzc3VlQ29tbWVudDU5ODAzNTQ1OQ==,2444231,2020-03-12T06:57:01Z,2020-03-12T06:57:01Z,NONE,Me too! Then we have a good test case :-),"{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,578427969
https://github.com/pydata/xarray/issues/3853#issuecomment-598020815,https://api.github.com/repos/pydata/xarray/issues/3853,598020815,MDEyOklzc3VlQ29tbWVudDU5ODAyMDgxNQ==,2444231,2020-03-12T05:59:51Z,2020-03-12T05:59:51Z,NONE,"I can have a look at implementing this. Might be a nice opportunity to actually contribute to some of the packages I use every day ;-)
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,578427969
https://github.com/pydata/xarray/issues/3853#issuecomment-597491042,https://api.github.com/repos/pydata/xarray/issues/3853,597491042,MDEyOklzc3VlQ29tbWVudDU5NzQ5MTA0Mg==,2444231,2020-03-11T07:50:43Z,2020-03-11T07:50:43Z,NONE,"Apparently this is possible by setting an environmental variable: http://www.pyngl.ucar.edu/NioFormats.shtml#GRIB1-user-defined-parameter-tables
So, if I have my codetable at `/path/to/codetab`; I can set `NIO_GRIB_PTABLE_PATH=/path/to/codetab`. I'm honestly not too happy with this solution. Would it be possible to add something like `backend_env` to `open_dataset`; where I can specify environmental variables that are active during opening, and then restore the environment afterwards?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,578427969
https://github.com/pydata/xarray/issues/422#issuecomment-483705762,https://api.github.com/repos/pydata/xarray/issues/422,483705762,MDEyOklzc3VlQ29tbWVudDQ4MzcwNTc2Mg==,2444231,2019-04-16T15:16:23Z,2019-04-16T15:16:23Z,NONE,"Maybe a bad question, but is there a good jumping off point to gain some familiarity with the code base? It’s admittedly my first time looking at xarray from the inside...","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,84127296
https://github.com/pydata/xarray/issues/422#issuecomment-413104436,https://api.github.com/repos/pydata/xarray/issues/422,413104436,MDEyOklzc3VlQ29tbWVudDQxMzEwNDQzNg==,2444231,2018-08-15T06:17:12Z,2018-08-15T06:17:12Z,NONE,"Hi,
my research group recently discussed weighted averaging with x-array, and I was wondering if there had been any progress with implementing this? I'd be happy to get involved if help is needed.
Thanks!","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,84127296
https://github.com/pydata/xarray/issues/2066#issuecomment-382430172,https://api.github.com/repos/pydata/xarray/issues/2066,382430172,MDEyOklzc3VlQ29tbWVudDM4MjQzMDE3Mg==,2444231,2018-04-18T15:35:15Z,2018-04-18T15:35:15Z,NONE,"I’d be happy taking a shot at contributing an error catch for that. I assume that wouldn’t be too difficult, right?
On 18. Apr 2018, 15:21 +0200, Ryan Abernathey , wrote:
> I don’t think we should change the default, at it may have unintended consequences.
>
> I DO think we should catch this specific error and recommend to the user to try autoclose=True in the error message.
>
>
>
> > On Apr 18, 2018, at 5:47 AM, Paul Gierz wrote:
> >
> > That seemed to do the trick. Would it be worthwhile to consider putting the default value of autoclose=True in the method definition, or would that induce other problems?
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub, or mute the thread.
> >
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,315381649
https://github.com/pydata/xarray/issues/2066#issuecomment-382330380,https://api.github.com/repos/pydata/xarray/issues/2066,382330380,MDEyOklzc3VlQ29tbWVudDM4MjMzMDM4MA==,2444231,2018-04-18T09:47:49Z,2018-04-18T09:47:49Z,NONE,"That seemed to do the trick. Would it be worthwhile to consider putting the default value of `autoclose=True` in the method definition, or would that induce other problems?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,315381649