Open Lasall opened 1 year ago
prior to #7975 poetry completely ignored build requirements so you couldn't build anyway: this is progress!
preferred fix should be to avoid using pip at all and do more or less what Chef.prepare()
does (preferably reusing as much code as possible). That class already understands how to make use of poetry's pool of repositories.
if this is important to you... pull requests surely welcome...
As a workaround it is possible to define the PIP_INDEX_URL not as environment variable (which is ignored with pip --isolate
) but write it to global config /etc/pip.conf:
[global]
index-url = ...
-vvv
option) and have included the output below.Issue
Similar to https://github.com/python-poetry/poetry/issues/8377 I experience some issues after https://github.com/python-poetry/poetry/pull/7975 .
In my setup I can only use a private PyPi repo, access to pypi.org is not possible. Therefore I've configured a poetry default-priority source which works just fine. However when using an extension module starting with poetry version 1.6 it will actually try to fetch the build requirements (from pypi.org). Since the pip-command is invoked with
--isolate
I don`t see a way to make it use my private repo for the build requirements as well.Example to reproduce this setup: https://github.com/Lasall/poetry-editable-extensions