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/5624#issuecomment-885278106,https://api.github.com/repos/pydata/xarray/issues/5624,885278106,IC_kwDOAMm_X840xEWa,1217238,2021-07-22T22:32:05Z,2021-07-22T22:32:05Z,MEMBER,@max-sixty I just pushed a commit with that change... let's verify that it works in CI and then ship it!,"{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,948890466
https://github.com/pydata/xarray/pull/5624#issuecomment-883620323,https://api.github.com/repos/pydata/xarray/issues/5624,883620323,IC_kwDOAMm_X840qvnj,1217238,2021-07-20T18:56:27Z,2021-07-20T18:56:27Z,MEMBER,"I think requiring typing-extensions for type checks to pass (especially internal to Xarray) would be totally reasonable. In general, it's not a big deal to install a dependency like this with pip/conda but every new dependency can be a marginal annoyance for those who maintain a custom build system of some sort.

To be honest, this only came up because I asked a co-worker to try using the development version of Xarray. Then they discovered that Apache-Beam currently puts on upper bound on the supported typing-extensions version (<= 3.7), so it would not be possible to install the latest versions of both Beam and Xarray :(. Beam should definitely relax this requirement, too, but it seemed like we do could the same, too.","{""total_count"": 2, ""+1"": 2, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,948890466