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/2888#issuecomment-660142287,https://api.github.com/repos/pydata/xarray/issues/2888,660142287,MDEyOklzc3VlQ29tbWVudDY2MDE0MjI4Nw==,601177,2020-07-17T14:36:57Z,2020-07-17T14:36:57Z,NONE,"Even if version information is (not yet) available, this would be very useful. Currently, when packaging xarray for downstream distributions, it is a very burdensome task to piece together which optional dependencies there are in the first place. I understand that dealing with the backlog makes this a rather tedious task, but making it a requirement going forward to add such dependency information whenever a dependency is changed or added would be required in any case.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,432058005
https://github.com/pydata/xarray/issues/2888#issuecomment-485922055,https://api.github.com/repos/pydata/xarray/issues/2888,485922055,MDEyOklzc3VlQ29tbWVudDQ4NTkyMjA1NQ==,240623,2019-04-23T18:31:02Z,2019-04-23T18:31:02Z,NONE,"WRT points:
- right, it's not tracked and that's the motivation for this issue
- just because it's not widely done is not a reason to ignore it and does not justify not doing it - IMO it is not widely done because many science projects are lapse in managing version dependencies using SEM-VER best practices, leaving it to the consumers, who are often clueless about these matters, to wonder why their project crashes with one or more dependencies that they don't understand nor care to dive into at any depth - many science projects avoid the whole problem by lagging with 0.x releases, failing to commit to stable, reliable APIs with at least 1.x releases - by adopting better SEM-VER practices, across the board, it should provide more confidence to arrive at 1.x releases.  But this is not my battle to wage, I'm just the messenger for thousands of consumers who have no idea what versions are compatible or not.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,432058005
https://github.com/pydata/xarray/issues/2888#issuecomment-485868641,https://api.github.com/repos/pydata/xarray/issues/2888,485868641,MDEyOklzc3VlQ29tbWVudDQ4NTg2ODY0MQ==,240623,2019-04-23T16:04:41Z,2019-04-23T16:18:40Z,NONE,"Since xarray is operating as a meta-package with various wrappers, it is the only place that can apply version compatibility on it's dependencies.  If there are optional dependencies, the python package extras are the process to manage them (not a README).  The SEM-VER standards allow specification of more than one version for any dependency (so long as it complies with SEM-VER standards).

Essentially, this is a request for more sophistication in the `setup.py` file
- https://github.com/pydata/xarray/blob/master/setup.py

Consider, for example, how Apache Airflow does it:
- https://github.com/apache/airflow/blob/master/setup.py
- https://github.com/apache/airflow/blob/master/setup.py#L353","{""total_count"": 1, ""+1"": 1, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,432058005