6.3.2: setuptools `build` failsSee 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
- Created 2 years ago
- Comments:12 (8 by maintainers)
Top GitHub Comments
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 .
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.