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/7000#issuecomment-1279048760,https://api.github.com/repos/pydata/xarray/issues/7000,1279048760,IC_kwDOAMm_X85MPLw4,11756442,2022-10-14T13:59:06Z,2022-10-14T13:59:06Z,MEMBER,"> Couple of minor comments, then we can merge.
@headtr1ck GitHub is unhelpfully not showing me any comments. Can you share a screen shot or something so I can address them? Thanks!","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1363829843
https://github.com/pydata/xarray/pull/7000#issuecomment-1244154384,https://api.github.com/repos/pydata/xarray/issues/7000,1244154384,IC_kwDOAMm_X85KKEoQ,11756442,2022-09-12T18:49:37Z,2022-09-12T18:49:37Z,MEMBER,"> add `list_backends` under `Advanced API`
Turns out it was already available so I added it to the Advance API docs as well as https://docs.xarray.dev/en/stable/internals/how-to-add-new-backend.html.
@dcherian I'll bookmark adding it to https://tutorial.xarray.dev/advanced/backends/backends.html.
@Illviljan, in case you didn't see this prior discussion:
> > So what would the return type need to be to get a nice table representation, but also allow you to select out individual backend objects? A pandas object containing the backend objects? Some kind of BackendList class?
>
> ... I haven't dreamed up an answer to this question yet. We could set it up so that `__str__` instead returns a pandas series, but I don't see another way we can have a pretty `__str__` that will also directly feed into a nicely formated table for `avail_engines()`.
Do you have any suggestions?
Note: `avail_engines()` has been renamed to `show_engines()`","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1363829843
https://github.com/pydata/xarray/pull/7000#issuecomment-1243848597,https://api.github.com/repos/pydata/xarray/issues/7000,1243848597,IC_kwDOAMm_X85KI5-V,11756442,2022-09-12T14:43:04Z,2022-09-12T14:43:04Z,MEMBER,"> we also probably don't want to pollute xarray's public namespace with multiple functions that do basically the same thing. Though maybe as it's all behind the backends namespace that doesn't matter so much? Then we might have `list_backends` and `display_backends` or something?
Currently there is this method:
```
>>> xr.backends.plugins.list_engines()
{'scipy': , 'rasterio': , 'store': }
```
and here we're adding (essentially to more effectively and prettily surface the above results to the user):
```
>>> xr.backends.api.avail_engines()
Engine Description Documentation
scipy
rasterio
store
```
The goal that led us (@snowman2 @dcherian @scottyhq) to create the initial issue was giving the user an easy, obvious way to find out what engines were actually available to them in their current environment. In the process of figuring out how to do this, @snowman2 and I discovered that `list_engines()` already existed, we just needed to add the attributes we wanted to display, make it pretty, and put it somewhere a user might look for it. We can certainly change the name of `avail_engines()` to `display_backends()`. Is there then a dev need to have another version of `list_backends()`, or would a ""see also"" to `list_engines()` be a solution here?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1363829843
https://github.com/pydata/xarray/pull/7000#issuecomment-1241174924,https://api.github.com/repos/pydata/xarray/issues/7000,1241174924,IC_kwDOAMm_X85J-tOM,11756442,2022-09-08T20:03:11Z,2022-09-08T20:03:11Z,MEMBER,"> That would not display in a nice table though. But might be anyway nice to add ;)
Agreed. I added a `__str__` to the `BackendEntrypoint` class, but...
> So what would the return type need to be to get a nice table representation, but also allow you to select out individual backend objects? A pandas object containing the backend objects? Some kind of BackendList class?
... I haven't dreamed up an answer to this question yet. We could set it up so that `__str__` instead returns a pandas series, but I don't see another way we can have a pretty `__str__` that will also directly feed into a nicely formated table for `avail_engines()`.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1363829843
https://github.com/pydata/xarray/pull/7000#issuecomment-1239824690,https://api.github.com/repos/pydata/xarray/issues/7000,1239824690,IC_kwDOAMm_X85J5jky,11756442,2022-09-07T20:12:51Z,2022-09-07T20:12:51Z,MEMBER,"> I know that it is more work but I think it would be more beneficial to have this information formated nicely than simply returning some lists.
Sounds good - I'll make that happen!","{""total_count"": 1, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 1, ""rocket"": 0, ""eyes"": 0}",,1363829843
https://github.com/pydata/xarray/issues/4001#issuecomment-1234759741,https://api.github.com/repos/pydata/xarray/issues/4001,1234759741,IC_kwDOAMm_X85JmPA9,11756442,2022-09-01T20:42:11Z,2022-09-01T20:42:11Z,MEMBER,Just wanted to let you know that the hackmd notes link in the google calendar leads to a 404 (the one at the top of this issue works though). Google also says the calendar url is invalid if I try to add it to my calendar (even though it works in a browser).,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,606530049
https://github.com/pydata/xarray/issues/6577#issuecomment-1234746473,https://api.github.com/repos/pydata/xarray/issues/6577,1234746473,IC_kwDOAMm_X85JmLxp,11756442,2022-09-01T20:28:22Z,2022-09-01T20:28:22Z,MEMBER,I'm happy to work on this!,"{""total_count"": 3, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 3, ""eyes"": 0}",,1227144046