issue_comments: 485868641
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/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 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 |