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/7461#issuecomment-1517892096,https://api.github.com/repos/pydata/xarray/issues/7461,1517892096,IC_kwDOAMm_X85aeTIA,6213168,2023-04-21T14:07:08Z,2023-04-21T14:07:08Z,MEMBER,"It just occurred to me that xarray dropped Python 3.8 3 months before what NEP-29 recommends. I think this is a problem.
Let's continue this discussion on #7777.","{""total_count"": 3, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 1, ""heart"": 0, ""rocket"": 0, ""eyes"": 2}",,1550109629
https://github.com/pydata/xarray/pull/7461#issuecomment-1515950820,https://api.github.com/repos/pydata/xarray/issues/7461,1515950820,IC_kwDOAMm_X85aW5Lk,6213168,2023-04-20T08:43:19Z,2023-04-20T08:43:19Z,MEMBER,">
> This also breaks xarray on ubuntu 20.04 which ships with Python 3.8 and is supported until April 2025. Python 3.8 is also supported at least until October 2024.
Not investing effort to support 5 years old dependencies was a very conscious decision. This is not something unique we do; we simply adhere to NEP29: https://numpy.org/neps/nep-0029-deprecation_policy.html
If for whatever reason you want to use python shipped by ubuntu 20.04, as opposed to conda/venv/poetry/whatever, you should also be prepared to stick to older versions of the python packages. Note that 5 years is the duration of *security* support. I'm not personally aware of security issues in xarray since Python 3.8 was abandoned (I've been a bit out of the loop and I could be proven wrong), but in the unlikely event that one should arise in xarray, we would consider a backport to Python 3.8.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1550109629
https://github.com/pydata/xarray/pull/7461#issuecomment-1507163165,https://api.github.com/repos/pydata/xarray/issues/7461,1507163165,IC_kwDOAMm_X85Z1Xwd,6213168,2023-04-13T15:21:52Z,2023-04-13T15:21:52Z,MEMBER,"> I assume you have given this a lot of thought, but imho the minimum dependency versions should be decided according to features needed, not timing.
It's not based on timing.
The policy is there so that, when a developer finds that they have to do extra labour to support an old version of a dependency, they can instead drop the support for the old version without needing to seek approval from the maintainers.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,1550109629