6.3.2: setuptools `build` fails
See original GitHub issueOn 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 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).
Read more >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.
Read more >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 ...
Read more >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 ...
Read more >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 ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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:
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.