issue_comments: 388967090
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/817#issuecomment-388967090 | https://api.github.com/repos/pydata/xarray/issues/817 | 388967090 | MDEyOklzc3VlQ29tbWVudDM4ODk2NzA5MA== | 1217238 | 2018-05-14T21:21:45Z | 2018-05-14T21:21:45Z | MEMBER | The only way we could make reading a gzipped netCDF4 file is to load the entire file into memory. That's why we didn't support this before. It's also less relevant for netCDF4, because netCDF4 supports in-file compression directly. With netCDF3, we can use scipy's netcdf reader, which supports Python file objects. But netCDF4-Python does not support Python file objects. This issue is concerned about supporting paths ending with |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
146079798 |