On Fri, Jun 25, 2021 at 12:46 PM John Snow <js...@redhat.com> wrote: > > 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 support older
s/support support/support/ > 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 <js...@redhat.com> > --- > python/Makefile | 2 ++ > 1 file changed, 2 insertions(+) > Reviewed-by: Willian Rampazzo <willi...@redhat.com>
