-
Notifications
You must be signed in to change notification settings - Fork 54
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
requirements.txt not installable by pip when local package depends on another #147
Comments
Looking at it more closely, it seems to be plagued by the same issue as python-poetry/poetry#266, namely that package-b is moved to the temporary build directory and thus can't resolve the path to package-a. Sadly it doesn't seem to be fixed by python-poetry/poetry#2114 and, after scouring through the code, there doesn't seem to be an obvious way to obtain and send an equivalent of |
This is still an issue in 1.0.9, despite the recent dependency resolution- and inconsistency fixes.
|
@jyggen I'm not seeing this issue in 1.1.4 anymore. It was still occurring for me in 1.1. Are you still seeing it or can this be closed out? |
Seems like it's still occuring. Not the exact same error, but a similar one. I've updated the example code in OP to use latest Poetry.
As seen by the |
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: Docker (python:3.7-slim)
Poetry version: 1.1.4
Link of a Gist with the contents of your pyproject.toml file: https://github.com/jyggen/poetry-example
Issue
pip
is unable to install the dependencies using therequirements.txt
frompoetry export
when the main application is depending on the local path package B, and where package B in turn depends on local path package A. I've created a repository (see above) that can reliably reproduce the error by runningdocker build .
.Dependency Graph:
Example output:
I've also seen a related error (where a local package depends on another local package that's also required by the main app) occur in an actual project when trying to install the export output with pip, but haven't been able to create a reproducible case yet. The error output, however, is the following:
The text was updated successfully, but these errors were encountered: