-
-
Notifications
You must be signed in to change notification settings - Fork 611
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
pip-compile annotations should be relative to file they are in #1107
Comments
Hello @chaoflow, Thanks for the issue! I think it's impossible since pip-compile could re-resolve paths after the parsing, but this solution looks hacky. Would love to hear any other opinions. |
Could pip-compile
? Looks like it can. I'll try to put up a WIP PR that does this, and improves path determination (fixing the example problem in #1067). I think I'll need to change the type of Help is always welcome! |
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
I'm sorry say that #1650 has been rejected. To reduce the incidence of this issue's particular aspect of the relative path problem I'm thinking my personal wrapper scripts and functions should always change the working directory to the output file's folder before running |
When pip-compile adds annotations for packages from files included with
-r
it uses a path relative to the current directory pip-compile is called from, instead of relative to the file it is writing to.It should be
-r base.in
not-r requirements/base.in
(see below).This might be solved by #1067.
Environment Versions
Steps to replicate
requirements/base.in:
requirements/extra.in:
Expected result
extra.txt:
Actual result
extra.txt:
The text was updated successfully, but these errors were encountered: