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/5038#issuecomment-800572482,https://api.github.com/repos/pydata/xarray/issues/5038,800572482,MDEyOklzc3VlQ29tbWVudDgwMDU3MjQ4Mg==,6551424,2021-03-16T20:15:38Z,2021-03-16T20:15:38Z,NONE,"> My guess is that this started to fail because we moved the `setup_requires` entry to `pyproject.toml`, which means that if you don't use that you have to take care of the build dependencies yourself.
Current versions of setuptools use pip instead of easy_install, so moving the setup_requires back would result in setup.py reporting an error when it cannot find setuptools_scm and pip is not installed in the build chroot.
The pyproject.toml build-system.requires is not exclusive; PEP 517 `.get_requires_for_build_wheel()` will be added to it to create the complete list of build requirements; the pyproject.toml build-system.requires is only needed to bootstrap the build backend itself.
And since the build backend when run on its own does not support pyproject.toml, but setuptools_scm is an internal implementation detail of the build backend and NOT of the PEP 517 part of the story... I'd personally say that it belongs in setup.cfg `setup_requires` rather than pyproject.toml
YMMV","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-800565107,https://api.github.com/repos/pydata/xarray/issues/5038,800565107,MDEyOklzc3VlQ29tbWVudDgwMDU2NTEwNw==,490531,2021-03-16T20:03:33Z,2021-03-16T20:04:19Z,CONTRIBUTOR,"Thanks to both of you as well as @eli-schwartz, it was indeed `setuptools-scm` missing (and apparently had been since 0.15.0, but previous `setuptools` version were silently downloading it through `easy_install` it seems).","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-800289142,https://api.github.com/repos/pydata/xarray/issues/5038,800289142,MDEyOklzc3VlQ29tbWVudDgwMDI4OTE0Mg==,11718923,2021-03-16T14:09:57Z,2021-03-16T14:41:32Z,NONE,"We should not be using build in arch packaging yet as other team members do not like pip as a wheel installer. We are working on that in https://github.com/pradyunsg/installer.
Can you see if setting `SETUPTOOLS_SCM_PRETEND_VERSION` solves your issue?
https://github.com/archlinux/svntogit-community/blob/d5d26f0836c57a20cbd6162a301c78ea60fc0845/trunk/PKGBUILD#L20
If setuptools-scm can't find a version I don't understand why it isn't falling back to `999`. @keewis, did anyone actually test this change?
https://github.com/pydata/xarray/blob/master/setup.py#L4
If what I said doesn't work, please try adding `python-toml` to `makedepends` so that setuptools picks up `pyproject.toml`.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-800312893,https://api.github.com/repos/pydata/xarray/issues/5038,800312893,MDEyOklzc3VlQ29tbWVudDgwMDMxMjg5Mw==,11718923,2021-03-16T14:35:37Z,2021-03-16T14:35:37Z,NONE,That is fine. @ArchangeGabriel this should be solved by adding `python-setuptools-scm` to `makedepends` and then either building from git or a PyPI tarball (sdist) or setting `SETUPTOOLS_SCM_PRETEND_VERSION`.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-800309366,https://api.github.com/repos/pydata/xarray/issues/5038,800309366,MDEyOklzc3VlQ29tbWVudDgwMDMwOTM2Ng==,14808389,2021-03-16T14:31:31Z,2021-03-16T14:31:31Z,MEMBER,"> I don't understand why it isn't falling back to `999`
I can reproduce the failure in an environment without `setuptools-scm`. If I install it everything works as expected. My guess is that this started to fail because we moved the `setup_requires` entry to `pyproject.toml`, which means that if you don't use that you have to take care of the build dependencies yourself.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-800169491,https://api.github.com/repos/pydata/xarray/issues/5038,800169491,MDEyOklzc3VlQ29tbWVudDgwMDE2OTQ5MQ==,14808389,2021-03-16T11:12:48Z,2021-03-16T11:12:48Z,MEMBER,"actually, it seems you *can* use `python setup.py install --prefix $PREFIX` if you have `setuptools_scm` installed. You'll find other build time dependencies in `pyproject.toml`.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-800164034,https://api.github.com/repos/pydata/xarray/issues/5038,800164034,MDEyOklzc3VlQ29tbWVudDgwMDE2NDAzNA==,490531,2021-03-16T11:03:51Z,2021-03-16T11:03:51Z,CONTRIBUTOR,"I’ve used the [one from Pypi](https://files.pythonhosted.org/packages/source/x/xarray/xarray-0.17.0.tar.gz).
I’ll check with @FFY00 whether I should be switching to `build` then.","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-800159060,https://api.github.com/repos/pydata/xarray/issues/5038,800159060,MDEyOklzc3VlQ29tbWVudDgwMDE1OTA2MA==,14808389,2021-03-16T10:56:46Z,2021-03-16T10:56:46Z,MEMBER,Where did you get the tarball from? If you used the one from github you need to use a PEP517 frontend (e.g. [`build`](https://github.com/pypa/build) or `pip`) to build the actual tarball: `setuptools_scm_git_archive` is only mentioned in `pyproject.toml`.,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-799982702,https://api.github.com/repos/pydata/xarray/issues/5038,799982702,MDEyOklzc3VlQ29tbWVudDc5OTk4MjcwMg==,490531,2021-03-16T06:12:05Z,2021-03-16T06:12:05Z,CONTRIBUTOR,"Actually while disabling tests and keeping on packaging, I indeed see a reported version of 0.0.0 for xarray. Our diff checker grabbed this:
```
usr/lib/python3.9/site-packages/xarray-0.16.2-py3.9.egg-info/ | usr/lib/python3.9/site-packages/xarray-0.0.0-py3.9.egg-info/
```
So maybe there is something wrong in the 0.17.0 tarball?","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-799980456,https://api.github.com/repos/pydata/xarray/issues/5038,799980456,MDEyOklzc3VlQ29tbWVudDc5OTk4MDQ1Ng==,490531,2021-03-16T06:07:37Z,2021-03-16T06:07:37Z,CONTRIBUTOR,"It’s not installed, I’m building it from source. So I run those command from within the cloned tarball:
```
python setup.py build
pytest --deselect xarray/tests/test_distributed.py::test_serializable_locks
```","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698
https://github.com/pydata/xarray/issues/5038#issuecomment-799958657,https://api.github.com/repos/pydata/xarray/issues/5038,799958657,MDEyOklzc3VlQ29tbWVudDc5OTk1ODY1Nw==,2443309,2021-03-16T05:21:12Z,2021-03-16T05:21:12Z,MEMBER,Thanks for the report. Can you say more about how you installed Xarray?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,832404698