-
Notifications
You must be signed in to change notification settings - Fork 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
PEP 517 builds cannot resolve directory dependencies #9716
Labels
resolution: invalid
Invalid issue/PR
Comments
AndrewGuenther
added
S: needs triage
Issues/PRs that need to be triaged
type: bug
A confirmed bug or unintended behavior
labels
Mar 21, 2021
3 tasks
Relative paths in a package is a non-standard Poetry extension. The build is handled by Poetry, so it should either reject this with a clear message, or somehow support it for you. pip can't do much about this. |
uranusjr
added
resolution: invalid
Invalid issue/PR
and removed
S: needs triage
Issues/PRs that need to be triaged
type: bug
A confirmed bug or unintended behavior
labels
Mar 21, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
pip version
21.0.1
Python version
3.8.5
OS
Linux, Ubuntu 20.04
Additional information
Relevant pyproject.toml bits:
Poetry is an illustrative example here, but the root cause lies within pip (or possibly even PEP 517)
Description
When performing a PEP 517 build, pip creates an isolated environment for the build to execute in within a temporary directory. No information about the directory the build originated from is shared with the build backend. As a result, any dependencies specified as a relative file/folder path cannot be resolved.
Expected behavior
Relative directory dependencies can be resolved in a PEP 517 build
How to Reproduce
pip install .
Output
Most of this output is from poetry, but including here for completeness
Code of Conduct
The text was updated successfully, but these errors were encountered: