issues: 395328437
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 395328437 | MDU6SXNzdWUzOTUzMjg0Mzc= | 2641 | pytest-runner should not be a hard-requirement in setup.py | 1217238 | closed | 0 | 0 | 2019-01-02T17:57:15Z | 2019-01-03T01:14:38Z | 2019-01-03T01:14:38Z | MEMBER | https://github.com/pydata/xarray/pull/2573 (by @horta) added This had the unintentional consequence of making pytest-runner a requirement for installing xarray. This is causing our conda-forge deployment to fail: https://github.com/conda-forge/xarray-feedstock/pull/42 We really want a "conditional requirement" only for testing as described in the pytest-runner docs: https://pypi.org/project/pytest-runner/ My plan is to do the conditional requirement, and back-port the commit to make a new 0.11.2 release. |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2641/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
completed | 13221727 | issue |