LookupError when using build-system dependencies relying on setuptools-scm

[btschwertfeger]

We built a package, lets name it "foo-versioning" based on setuptools-scm. foo-versioning has setuptools-scm as its runtime dependency.

Package foo-versioning uses setuptools-scm and extends it to match our company-internal versioning requirements.

Since setuptools-scm v9.0.0, building our packages no longer works with "foo-versioning" in build-system.requires in pyproject.toml

Error message:

LookupError: pyproject.toml does not contain a tool.setuptools_scm section. setuptools_scm requires configuration via either:
        1. [tool.setuptools_scm] section in pyproject.toml, or
        2. setuptools_scm (or setuptools-scm) in [build-system] requires

This can currently only be fixed, either by adding setuptools-scm to the build-system.requires of all our packages that depend on foo-versioning or adding the tool.setuptools_scm section into the pyproject.toml. This is not desirable, since then we not only need to touch all our projects, but also need to manage their version constraints at multiple places.

Ideally we don't need to configure setuptools-scm in pyproject.toml, as long as we use our foo-versioning package that depends on and extends setuptools-scm.

[RonnyPfannschmidt]

thats a regression in config parsing the release was yanked, bugfix incoming