-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Private registries not taken into consideration in local dependencies #2221
Comments
Today, I tried a much simpler scenario, and I'm still stuck. I'm not sure what poetry does, that breaks pip... Given the following pyproject.toml:
With this, Unfortunately:
However, if I run the exact same thing (outside of a virtual environment), it works:
I'm thinking there may be an environment variable to blame here 🤔 |
I found a way to fix it... I can't explain why though. https://github.com/python-poetry/poetry/blob/master/poetry/utils/env.py#L889 Adding (should I write a separate issue?) |
@jonapich I had exactly the same issue and I found that my virtual environment used It looks like when a virtual environment gets created, it installs pip version that was bundled together with the required python release ( |
This does not reproduce on 1.2.x with the new installer -- please open a new issue if you believe you have run into something related. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).OS version and name: Ubuntu 18.04
Poetry version: 1.0.5
Issue
When you reference a local path as a dependency, and that reference has a registry setup, it's not taken into account during
poetry install
:in repo/bigproject/pyproject.toml:
in repo/local-dep/pyproject.toml:
repo/local-dep
just fine (it checks the private repo 👍)repo/bigproject
; it will not attempt to use the private registryWorkaround: Add the repo information in
repo/bigproject/pyproject.toml
even though it doesn't technically needs it.Sidenote: Overall the local dependencies feature seems to have opened a can of worms. For instance:
this-lib = 'somepath/../someotherpath/../this-lib/
where it should just bethis-lib/
.pyproject.toml
file location and it will eventually fail saying the local package cannot be found.The text was updated successfully, but these errors were encountered: