python: remove auto-generated pyproject.toml file
authorJohn Snow <jsnow@redhat.com>
Tue, 29 Jun 2021 21:43:22 +0000 (17:43 -0400)
committerJohn Snow <jsnow@redhat.com>
Thu, 1 Jul 2021 01:57:08 +0000 (21:57 -0400)
For reasons that at-present escape me, pipenv insists on creating a stub
pyproject.toml file. This file is a nuisance, because its mere presence
changes the behavior of various tools.

For instance, this stub file will cause "pip install --user -e ." to
fail in spectacular fashion with misleading errors. "pip install -e ."
works okay, but for some reason pip does not support editable installs
to the user directory when using PEP517.

References:
  https://github.com/pypa/pip/pull/9990
  https://github.com/pypa/pip/issues/7953

As outlined in ea1213b7ccc, it is still too early for us to consider
moving to a PEP-517 exclusive package. We must support older
distributions, so squash the annoyance for now. (Python 3.6 shipped Dec
2016, PEP517 support showed up in pip sometime in 2019 or so.)

Add 'pyproject.toml' to the 'make clean' target, and also delete it
after every pipenv invocation issued by the Makefile.

Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Message-id: 20210629214323.1329806-15-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
python/Makefile

index 0432ee00222f423fdbc8e57eb0d899acec17f7fc..ac46ae33e7adbe1286d4d1c7dc33147dfac78117 100644 (file)
@@ -49,6 +49,7 @@ help:
 pipenv: .venv
 .venv: Pipfile.lock
        @PIPENV_VENV_IN_PROJECT=1 pipenv sync --dev --keep-outdated
+       rm -f pyproject.toml
        @touch .venv
 
 .PHONY: check-pipenv
@@ -91,6 +92,7 @@ check-tox:
 .PHONY: clean
 clean:
        python3 setup.py clean --all
+       rm -f pyproject.toml
 
 .PHONY: distclean
 distclean: clean