pull_requests: 469745175
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | auto_merge | repo | url | merged_by |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 469745175 | MDExOlB1bGxSZXF1ZXN0NDY5NzQ1MTc1 | 4350 | closed | 0 | install the project on RTD | 14808389 | The versions were broken because instead of installing we simply extended `sys.path`. That way, `sphinx` is able to find the correct version, but `setuptools_scm` can't put the version in the `METADATA` file in the installed egg. Instead, `pkg_resources.get_distribution("xarray").version` gets its version from a released version of `xarray` that was pulled in by a dependency (hence the old version in the title bar). To fix that, we need to install before building the documentation. However, since RTD installs with `--upgrade --upgrade-strategy=eager` (which upgrades all packages to the most recent version), we can't install using their `pip` method. The `setuptools` method doesn't work either because `cfgrib` pulls in the most recent released version of `xarray`, and `setuptools` can't seem to overwrite / uninstall previously installed versions. To work around that, this installs using the `pip` section in the environment file. - [x] Closes #4289 | 2020-08-18T21:01:59Z | 2020-08-18T22:33:10Z | 2020-08-18T22:32:51Z | 2020-08-18T22:32:50Z | 11d72d0eb7a0c5176b2543c497cd454a7f9c881e | 0 | f57166f71d92a10b71db06e5fda1cd5bada4d8e5 | 5198360c0bc28dd7528e909c6b6ccffe731474ad | MEMBER | 13221727 | https://github.com/pydata/xarray/pull/4350 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests