[Bug 267040] devel/py-nbformat and devel/py-black incorrectly install files belonging to the test infrastructure

From: <bugzilla-noreply_at_freebsd.org>
Date: Thu, 20 Oct 2022 21:05:41 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267040

Kai Knoblich <kai@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kai@FreeBSD.org

--- Comment #5 from Kai Knoblich <kai@FreeBSD.org> ---
Created attachment 237489
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=237489&action=edit
py-black-fix-packaging-issues.patch

The current version of devel/py-black is still broken as it has packaging
issues. The games/anki port, which requires devel/py-black for build, also
fails to build due this regression.

For instance if one tries to do a

> $ python3.9 -m black
> /usr/local/bin/python3.9: No module named black

or even try to run the script "black"

> $ black
> Traceback (most recent call last):
>   File "/usr/local/bin/black", line 33, in <module>
>     sys.exit(load_entry_point('black==22.10.0', 'console_scripts', 'black')())
>   File "/usr/local/bin/black", line 25, in importlib_load_entry_point
>     return next(matches).load()
>   File "/usr/local/lib/python3.9/importlib/metadata.py", line 86, in load
>     module = import_module(match.group('module'))
>   File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in > import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
>   File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
>   File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
>   File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked
> ModuleNotFoundError: No module named 'black'

Attached is a patch that should remedy the packaging issues. (At least
games/anki builds fine so far and I haven't had the time to do a bulk run
against all consumers of devel/py-black, yet).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.