pythonpypa/setuptools-scm #941Not a task: already works

Is it neccessary to pull in rich as build-backend depndency?

envgap__pypa__setuptools-scm-941

Original GitHub issue ↗Dated source checkout ↗Opened 2023-09-26

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

The project already builds and runs before the fix, so there is nothing to repair.

02 / ENVIRONMENT RECIPE

Base commit: 6ab652e2beef00947d9a14cd2834a037ed4795db
Manifest: pyproject.toml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

pypa/setuptools-scm #941 · read the original issue

Hello,

I've noticed version 8 now declares a build-backend dependency on rich:



https://github.com/pypa/setuptools_scm/blob/6ab652e2beef00947d9a14cd2834a037ed4795db/pyproject.toml#L3-L6



However, the build works without rich. I assume that's because the import is try-expected:



https://github.com/pypa/setuptools_scm/blob/6ab652e2beef00947d9a14cd2834a037ed4795db/src/setuptools_scm/_log.py#L32-L42



In Fedora Linux, I plan to patch this out to simplify the bootstrap of our Python packages for the next Python version. However, I was wondering if this should actually be a build dependency. Why is it?

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]