git archive --prefix /usr/ports/ HEAD, TAKES Forever and is called for each Python component build. HOW TO MITIGATE?

[beckerwilliams]

When building ports that rely on python, I see 'git archive --prefix /usr/ports/ HEAD' being called after EACH python component build.
* Building wheel...

...
/usr/local/lib/python3.11/site-packages/setuptools/config/pyprojecttoml.py:104: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*.
warnings.warn(msg, _BetaConfiguration)
running bdist_wheel
running build
running build_py
creating build
creating build/lib.freebsd-14.3-PRERELEASE-amd64-cpython-311
creating build/lib.freebsd-14.3-PRERELEASE-amd64-cpython-311/maturin
copying maturin/__main__.py -> build/lib.freebsd-14.3-PRERELEASE-amd64-cpython-311/maturin
copying maturin/__init__.py -> build/lib.freebsd-14.3-PRERELEASE-amd64-cpython-311/maturin
running egg_info
writing maturin.egg-info/PKG-INFO
writing dependency_links to maturin.egg-info/dependency_links.txt
writing requirements to maturin.egg-info/requires.txt
writing top-level names to maturin.egg-info/top_level.txt

And then is observed git archive, doing its slooowwwww thing ...

PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND

6871 root 1 20 0 182M 166M piperd 2 0:08 0.38% /usr/local/bin/python3.11 /usr/local/lib/python3.11/site-packages/
7171 root 1 68 0 1533M 524M RUN 2 0:03 0.19% git archive --prefix /usr/ports/ HEAD

Killing the 'git archive --prefix /usr/ports/ HEAD' process allows the build to continue, with unknown results.

Is GIT ARCHIVE Really needed Every Python Package Build?


Any insights?