Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

6.3.2: setuptools `build` fails

See original GitHub issue

On using sdist source tar ball setuptools build command fails

+ /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -s'
running build
running build_py
creating build
creating build/lib
creating build/lib/diff_cover
copying diff_cover/__init__.py -> build/lib/diff_cover
copying diff_cover/command_runner.py -> build/lib/diff_cover
copying diff_cover/config_parser.py -> build/lib/diff_cover
copying diff_cover/diff_cover_tool.py -> build/lib/diff_cover
copying diff_cover/diff_quality_tool.py -> build/lib/diff_cover
copying diff_cover/diff_reporter.py -> build/lib/diff_cover
copying diff_cover/git_diff.py -> build/lib/diff_cover
copying diff_cover/git_path.py -> build/lib/diff_cover
copying diff_cover/hook.py -> build/lib/diff_cover
copying diff_cover/hookspecs.py -> build/lib/diff_cover
copying diff_cover/report_generator.py -> build/lib/diff_cover
copying diff_cover/snippets.py -> build/lib/diff_cover
copying diff_cover/util.py -> build/lib/diff_cover
creating build/lib/diff_cover/violationsreporters
copying diff_cover/violationsreporters/__init__.py -> build/lib/diff_cover/violationsreporters
copying diff_cover/violationsreporters/base.py -> build/lib/diff_cover/violationsreporters
copying diff_cover/violationsreporters/java_violations_reporter.py -> build/lib/diff_cover/violationsreporters
copying diff_cover/violationsreporters/violations_reporter.py -> build/lib/diff_cover/violationsreporters
error: package directory 'violationsreporters' does not exist

Issue Analytics

State:
Created 2 years ago
Comments:12 (8 by maintainers)

Top GitHub Comments

2reactions

Bachmann1234commented, Aug 20, 2021

Im out of town for a few days but I’ll look into it next week.

On Fri, Aug 20, 2021, 4:25 AM Tomasz Kłoczko @.***> wrote:

If may I mention yet another small thing … 😃 Just found that git tree contains bits which are not present in sdist like tests/. Is it possible to add those files as well to the sdist to allow use it on building packages? (I’m obligatory trying to include in my packages build procedures execution of the test suites).

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/Bachmann1234/diff_cover/issues/244#issuecomment-902525920, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALTLRP5GZBQCJUVD7YXT33T5YGPZANCNFSM5CPCPCUQ .

0reactions

Bachmann1234commented, Aug 30, 2021

Right, you can’t compile the test fixtures. They are not intended to be ran or imported in any way they are not executable code. that directory is not a a module (no init.py)

But the point is moot as the most recent version removed the test directory as it pollutes site packages.

Top Results From Across the Web

build failure with setuptools_scm 6.0.1 · Issue #541 - GitHub

1, pip install setuptools-scm would work correctly, but pip install executing would not ( executing has setuptools_scm as a dependency).

History - setuptools 65.6.3.post20221220 documentation

Future releases of setuptools may simply ignore externally set metadata not backed by dynamic or even halt the build with an error.

check-manifest fails after upgrading setuptools_scm from 6.0.1 ...

This issue caused due to a bug in the check-manifest library where the sdist filenames containing dashes were being parsed incorrectly when ...

ERROR: setuptools==41.0.0 is used in combination with ...

20:31:15 /src/.eggs/setuptools_scm-6.3.2-py3.7.egg/setuptools_scm/ ... This happens as setuptools is unable to replace itself when a activated build ...

setuptools-scm - PyPI

setuptools_scm. setuptools_scm extracts Python package versions from git or hg metadata instead of declaring them as the version argument or in a SCM ......