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/3297#issuecomment-530680614,https://api.github.com/repos/pydata/xarray/issues/3297,530680614,MDEyOklzc3VlQ29tbWVudDUzMDY4MDYxNA==,22542812,2019-09-12T06:11:02Z,2019-09-12T06:11:02Z,NONE,"Sorry for the slow response, I have little time at the moment. The option `invalid_netcdf=True` is not yet in the latest release, is it? I get an `TypeError`. 
I would have to use a manually installed version of `xarray` to use it, right?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,491215043
https://github.com/pydata/xarray/issues/3297#issuecomment-529689580,https://api.github.com/repos/pydata/xarray/issues/3297,529689580,MDEyOklzc3VlQ29tbWVudDUyOTY4OTU4MA==,22542812,2019-09-09T22:20:08Z,2019-09-09T22:20:08Z,NONE,"I agree that including it in NetCDF is the 'most sane' approach. I don't really know how much work it is, expanding the standard.

To be honest, I don't really care about NetCDF, for me `xarray` is just an incredible good way to make code more stable and readable (though it still has several usability issues). In my community everyone uses HDF5 anyway, so dropping compatibility is no big issue. I just want a way to persist data as it is and conveniently load it for plotting and post processing.

I would still encourage you to push saving of complex data. In most fields people use complex data and it is hard to convince them that they benefit from this great library, if saving simple data takes complicated keyword arguments and annoys you with warnings compared to a simple `np.savez` on regular `ndarray`s.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,491215043