issue_comments
15 rows where author_association = "MEMBER" and issue = 715730538 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- deprecate pynio backend · 15 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
1320965798 | https://github.com/pydata/xarray/issues/4491#issuecomment-1320965798 | https://api.github.com/repos/pydata/xarray/issues/4491 | IC_kwDOAMm_X85OvFam | jhamman 2443309 | 2022-11-19T20:46:10Z | 2022-11-19T20:46:10Z | MEMBER | I changed the title of this issue to reflect the current situation. PyNIO is unlikely to have another release and its compatibility with the Xarray and the rest of the ecosystem is quickly waning. If someone decides to pick up PyNIO maintenance in the future, they can provide backend entrypoint. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
1320669382 | https://github.com/pydata/xarray/issues/4491#issuecomment-1320669382 | https://api.github.com/repos/pydata/xarray/issues/4491 | IC_kwDOAMm_X85Ot9DG | jhamman 2443309 | 2022-11-18T23:54:07Z | 2022-11-18T23:54:07Z | MEMBER | I suggest we plan to remove the pynio backend in a future release. The project is very likely dead. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
1115470489 | https://github.com/pydata/xarray/issues/4491#issuecomment-1115470489 | https://api.github.com/repos/pydata/xarray/issues/4491 | IC_kwDOAMm_X85CfLqZ | dcherian 2448579 | 2022-05-02T23:40:08Z | 2022-05-02T23:40:21Z | MEMBER | Yes it works now but not after I updated dask and scipy versions in #6559 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
1115287736 | https://github.com/pydata/xarray/issues/4491#issuecomment-1115287736 | https://api.github.com/repos/pydata/xarray/issues/4491 | IC_kwDOAMm_X85CefC4 | dcherian 2448579 | 2022-05-02T19:39:59Z | 2022-05-02T19:39:59Z | MEMBER | 6559 is dropping PyNIO because I can't create a |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
1086647600 | https://github.com/pydata/xarray/issues/4491#issuecomment-1086647600 | https://api.github.com/repos/pydata/xarray/issues/4491 | IC_kwDOAMm_X85AxO0w | mathause 10194086 | 2022-04-02T14:02:50Z | 2022-04-02T14:02:50Z | MEMBER | We can uncomment here: which adds it back to the test suite. As the version does not change, the new build should also be picked up from (it's nice to see that the build for pynio is fixed, but the package itself does not seem to be actively maintained). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
786678671 | https://github.com/pydata/xarray/issues/4491#issuecomment-786678671 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDc4NjY3ODY3MQ== | dcherian 2448579 | 2021-02-26T14:26:02Z | 2021-02-26T14:26:02Z | MEMBER |
I think this is OK. The README should say that it is totally unmaintained. cc @khallock for awareness. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
786660516 | https://github.com/pydata/xarray/issues/4491#issuecomment-786660516 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDc4NjY2MDUxNg== | keewis 14808389 | 2021-02-26T13:52:55Z | 2021-02-26T13:52:55Z | MEMBER | I agree, that would probably be the best place to put it. We might want do the same for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
786655192 | https://github.com/pydata/xarray/issues/4491#issuecomment-786655192 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDc4NjY1NTE5Mg== | mathause 10194086 | 2021-02-26T13:42:33Z | 2021-02-26T13:42:33Z | MEMBER | That would be nice. I would probably call it "xarray-pynio" (?) and move it to the "xarray-contrib" organisation. However, I think this needs a higher-level decision. |
{ "total_count": 2, "+1": 2, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
786492109 | https://github.com/pydata/xarray/issues/4491#issuecomment-786492109 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDc4NjQ5MjEwOQ== | mathause 10194086 | 2021-02-26T08:27:50Z | 2021-02-26T08:27:50Z | MEMBER | We just bumped the the minimum version of python-netCDF4 to 1.5 - we won't be able to bump it to 1.6 because of this. So we'll need to decide what to do with pynio before and properly deprecate it. Worth noting though, that there is no python-netCDF4 version 1.6 at the moment, so this is not all that urgent. netCDF4 has not released a minor version in a long time (March 2019) (but they have done 12 patch releases). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
706737872 | https://github.com/pydata/xarray/issues/4491#issuecomment-706737872 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDcwNjczNzg3Mg== | mathause 10194086 | 2020-10-11T17:22:19Z | 2020-10-11T17:22:19Z | MEMBER | 4492 is merged. I changed the title to reflect that pynio should eventually be moved to an external repo but keep the issue open to have the discussion in place. I hope that this should not be too hard after the backend refactor. |
{ "total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
705143832 | https://github.com/pydata/xarray/issues/4491#issuecomment-705143832 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDcwNTE0MzgzMg== | mathause 10194086 | 2020-10-07T19:22:46Z | 2020-10-07T19:22:46Z | MEMBER |
Yes, fine for me - check #4492 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
705004706 | https://github.com/pydata/xarray/issues/4491#issuecomment-705004706 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDcwNTAwNDcwNg== | dcherian 2448579 | 2020-10-07T15:14:14Z | 2020-10-07T15:14:14Z | MEMBER |
This sounds fine to me. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
705002119 | https://github.com/pydata/xarray/issues/4491#issuecomment-705002119 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDcwNTAwMjExOQ== | keewis 14808389 | 2020-10-07T15:10:08Z | 2020-10-07T15:11:20Z | MEMBER | not sure if we should repurpose Would it be enough to only test using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
704907241 | https://github.com/pydata/xarray/issues/4491#issuecomment-704907241 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDcwNDkwNzI0MQ== | mathause 10194086 | 2020-10-07T12:39:38Z | 2020-10-07T12:39:38Z | MEMBER | In Keep pynio in
- Remove pynio from:
- Do you agree? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
deprecate pynio backend 715730538 | |
704685163 | https://github.com/pydata/xarray/issues/4491#issuecomment-704685163 | https://api.github.com/repos/pydata/xarray/issues/4491 | MDEyOklzc3VlQ29tbWVudDcwNDY4NTE2Mw== | shoyer 1217238 | 2020-10-07T04:33:38Z | 2020-10-07T04:33:38Z | MEMBER |
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 } |
deprecate pynio backend 715730538 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE [issue_comments] ( [html_url] TEXT, [issue_url] TEXT, [id] INTEGER PRIMARY KEY, [node_id] TEXT, [user] INTEGER REFERENCES [users]([id]), [created_at] TEXT, [updated_at] TEXT, [author_association] TEXT, [body] TEXT, [reactions] TEXT, [performed_via_github_app] TEXT, [issue] INTEGER REFERENCES [issues]([id]) ); CREATE INDEX [idx_issue_comments_issue] ON [issue_comments] ([issue]); CREATE INDEX [idx_issue_comments_user] ON [issue_comments] ([user]);
user 5