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/4491#issuecomment-704685163,https://api.github.com/repos/pydata/xarray/issues/4491,704685163,MDEyOklzc3VlQ29tbWVudDcwNDY4NTE2Mw==,1217238,2020-10-07T04:33:38Z,2020-10-07T04:33:38Z,MEMBER,"> And long term what to do with the pynio backend? Deprecate? Move to an external repo?

Yes, in the long term I think the pynio backend will need to be moved outside of xarray, along with backends for other unmaintained projects such as pydap. This is one of goals of the backend refactor effort lead by @alexamici and @aurghs.

Until that happens, if new versions of netCDF4 and pynio are incompatible, my preferred work-around would be to reduce test coverage for pynio. It's not being developed actively, so there aren't strong reasons to maintain test coverage with every version of Python.","{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,715730538