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/4987#issuecomment-796925819,https://api.github.com/repos/pydata/xarray/issues/4987,796925819,MDEyOklzc3VlQ29tbWVudDc5NjkyNTgxOQ==,5635139,2021-03-11T17:55:28Z,2021-03-11T17:55:28Z,MEMBER,"> Not at this point. We just released 0.17 so I would think we're at least a week or two away from 0.18.

Just to set expectations — I hadn't thought we were releasing so soon — though I'd be happy to, and it's getting easier & easier to do releases.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,820480606
https://github.com/pydata/xarray/issues/4987#issuecomment-796919656,https://api.github.com/repos/pydata/xarray/issues/4987,796919656,MDEyOklzc3VlQ29tbWVudDc5NjkxOTY1Ng==,2443309,2021-03-11T17:46:18Z,2021-03-11T17:46:18Z,MEMBER,Not at this point. We just released 0.17 so I would think we're at least a week or two away from 0.18. ,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,820480606
https://github.com/pydata/xarray/issues/4987#issuecomment-791681130,https://api.github.com/repos/pydata/xarray/issues/4987,791681130,MDEyOklzc3VlQ29tbWVudDc5MTY4MTEzMA==,2443309,2021-03-05T20:52:06Z,2021-03-05T20:52:06Z,MEMBER,#4989 includes the full refactor. The plan is to merge this to xarray/master on Monday.,"{""total_count"": 1, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 1, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,820480606
https://github.com/pydata/xarray/issues/4987#issuecomment-790782639,https://api.github.com/repos/pydata/xarray/issues/4987,790782639,MDEyOklzc3VlQ29tbWVudDc5MDc4MjYzOQ==,226037,2021-03-04T17:16:48Z,2021-03-04T17:22:31Z,MEMBER,"@jp-dark it is in fact possible to write an _xarray_ backend without explicitly depending on _xarray_ in your `setup.py` if you put all your backend glue code in a separate module not imported by the main `__init__.py`.

We use the setuptools entrypoints infrastructure that triggers a module load only from within _xarray_ itself.

This is still work in progress, but we are implementing this strategy in _cfgrib_ with success. You can get inspiration from the following PR by @aurghs:

https://github.com/ecmwf/cfgrib/pull/203
","{""total_count"": 2, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 2, ""rocket"": 0, ""eyes"": 0}",,820480606
https://github.com/pydata/xarray/issues/4987#issuecomment-790140398,https://api.github.com/repos/pydata/xarray/issues/4987,790140398,MDEyOklzc3VlQ29tbWVudDc5MDE0MDM5OA==,1217238,2021-03-03T23:12:37Z,2021-03-03T23:12:37Z,MEMBER,"@jp-dark How would you feel about writing another small library, e.g., ""xarray-tiledb"" that can explicitly depend on both xarray and tiledb?

We can potentially do some of xarray's backend stuff with protocols, but there are some aspects (especially for more advanced features like lazy loading) that will likely need the hard xarray dependency.","{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,820480606
https://github.com/pydata/xarray/issues/4987#issuecomment-790024577,https://api.github.com/repos/pydata/xarray/issues/4987,790024577,MDEyOklzc3VlQ29tbWVudDc5MDAyNDU3Nw==,2443309,2021-03-03T20:13:44Z,2021-03-03T20:13:44Z,MEMBER,This is a great spot @jp-dark! Looking forward to seeing your progress.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,820480606
https://github.com/pydata/xarray/issues/4987#issuecomment-789933725,https://api.github.com/repos/pydata/xarray/issues/4987,789933725,MDEyOklzc3VlQ29tbWVudDc4OTkzMzcyNQ==,2443309,2021-03-03T17:52:36Z,2021-03-03T17:54:38Z,MEMBER,"Hi @jp-dark! Thanks for opening this issue and the draft pull request in #4988. As you probably know, we're in the process of completing a major refactor of our storage backends system (see #4989 and #4810 for the current state of that work). One of the main feature additions in this work is the new entrypoints functionality which will allow backends (like TileDB) to declare backend support without including the code in the Xarray itself.

In light of this new functionality, we'd like to see if we can put the TileDB backend in TileDB itself (or in an another adjacent package). The end user functionality would be the same as the entrypoint would be registered at install time. We'd be happy to document the TileDB in the Xarray documentation as well.

This is the development pattern we are headed to with most of our backends, including some of the current backends. We'd be happy to help work with you to sort out the details as I'm sure there will be one or two early adopter bumps to work through. 

cc @alexamici @aurghs @shoyer ","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,820480606