issue_comments: 778631437
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/issues/4179#issuecomment-778631437 | https://api.github.com/repos/pydata/xarray/issues/4179 | 778631437 | MDEyOklzc3VlQ29tbWVudDc3ODYzMTQzNw== | 14808389 | 2021-02-13T15:05:46Z | 2021-02-13T20:02:19Z | MEMBER | actually, this version of the policy won't work: if we require the most recent python version from 42 months ago (Aug 2017) we get python 3.6, which we can't maintain because most of our dependencies won't support it anymore by the time we would be allowed to drop it. So I think we will have to find a way to work around that, either by changing the support window of python or follow NEP29 and require at least M supported versions, or something completely different. One edge case of the rules above would be if a package has no release for more than N months and then multiple releases over the course of a few weeks. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
645154872 |