-
Notifications
You must be signed in to change notification settings - Fork 707
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
Included requirements files should be relative to parent, not cwd #1416
Comments
I believe this is the same as #1367. |
Gonna look at it now. |
Thanks! I'll close this as a duplicate |
Do you know if pip has the same treatment for local packages, or is this just for requirements / constraints files? |
Ahh, I see, it's just files (not directories): pypa/pip#8765 |
Looks like pip is inconsistent, in that in the following case it is relative to cwd:
I don't care about^ case at all |
Okay yeah, makes sense. |
## Summary In a `requirements.txt` file, it turns out that the `-c` and `-r` entries should be interpreted as relative to the file in which they're declared, while the `-e` entries should be interpreted as relative to the current working directory, no matter where they're defined. Previously, we always used the current working directory; now, we use the declaring file's directory for `-c` and `-r`. Closes #1367. Closes #1416.
The text was updated successfully, but these errors were encountered: