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/5329#issuecomment-843824599,https://api.github.com/repos/pydata/xarray/issues/5329,843824599,MDEyOklzc3VlQ29tbWVudDg0MzgyNDU5OQ==,226037,2021-05-19T07:28:03Z,2021-05-19T07:28:03Z,MEMBER,"@shoyer and @pont-us my take is that `engine=None` is mostly and feature to help new users experiment with xarray. The logic for autodetecting the engine has always been extremely fragile and the result depends on what packages are installed on the system.

I think it is OK to add a dedicated `xarray.EngineGuessingError`, but I'd not try anything more complex and in general invite users to pass `engine` explicitly.

Examples of strings that identify a dataset when the right backend is installed, but are not paths and the `FileNotFoundError ` would sound confusing:
- `/vsizip/my.zip/my.tif` with `rioxarray`
- `https://myhost/myfile.nc` with `netcdf4` and others","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,894125618