issue_comments: 1243848597

This data as json

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-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': <xarray.backends.scipy_.ScipyBackendEntrypoint object at 0x101ec4ee0>, 'rasterio': <rioxarray.xarray_plugin.RasterioBackend object at 0x10217de70>, 'store': <xarray.backends.store.StoreBackendEntrypoint object at 0x10217de10>} 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 thatlist_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 ofavail_engines()todisplay_backends(). Is there then a dev need to have another version oflist_backends(), or would a "see also" tolist_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