issue_comments: 431463477
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/2492#issuecomment-431463477 | https://api.github.com/repos/pydata/xarray/issues/2492 | 431463477 | MDEyOklzc3VlQ29tbWVudDQzMTQ2MzQ3Nw== | 1924696 | 2018-10-19T18:55:13Z | 2018-10-19T18:55:13Z | NONE | @shoyer, I also agree that requiring a backend to be explicitly selected for grib files would be a better solution from a user experience perspective, as opposed to silently replacing PyNIO with cfgrib (inconsistent variable names would be a major concern). As @jhamman mentioned, we have been evaluating the long-term viability of PyNIO and are considering putting it into "maintenance mode". Unfortunately, the lead developer of PyNIO retired last year, and we don't have the budget to replace him at this time. We intend to continue fixing bugs in PyNIO as necessary (versions 1.5.1, 1.5.2, and 1.5.3 have all been released in the last three months), and we will also continue supporting the conda-forge/pynio-feedstock recipe. However, no new functionality (such as updating/adding grib tables) is part of our current long-term plan for PyNIO. (cc'ing @marylhaley in case she has any additional input to offer) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
371514413 |