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/5073#issuecomment-807145690,https://api.github.com/repos/pydata/xarray/issues/5073,807145690,MDEyOklzc3VlQ29tbWVudDgwNzE0NTY5MA==,14808389,2021-03-25T17:29:57Z,2021-03-25T17:30:57Z,MEMBER,"as far as I understand the docs of [`DeprecationWarning`](https://docs.python.org/3/library/exceptions.html#DeprecationWarning) and [`FutureWarning`](https://docs.python.org/3/library/exceptions.html#FutureWarning), the main difference is the intended target audience in a traditional library vs. application setting (where libraries are always used to write applications): `PendingDeprecationWarning` and `DeprecationWarning` are used to signal deprecations in the library, while `FutureWarning` are intended for users of the application. Interestingly, [PEP565](https://www.python.org/dev/peps/pep-0565/#additional-use-case-for-futurewarning) mentions that `FutureWarning` can also be used for changed semantics of valid code.

If we follow that, `xarray` should not issue `FutureWarning` (other than to report changing semantics) because it is a library and both interactive and scripted use would be similar to writing a application.","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,840258082