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 `<build-backend>.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-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