-
-
Notifications
You must be signed in to change notification settings - Fork 609
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
Dependency resolver issue #1271
Comments
Does a regular |
Yes:
|
That's because
Note:
Also:
|
|
Because you manually helped |
Thanks, but I unpinned it in the 5th step. So I don't understand 🤷 |
Yes, but it's still pinned to |
@atugushev Thank you for the clarification! |
Thanks for the issue! Don't hesitate to reach out if you have any other issues. |
I added the new unpinned package to a
requirements.in
file and I expected thepip-compile
solves dependencies automatically. However, I found it is not working as I expected. Also, I found thepip-compile
step depends also on the previous run.Environment Versions
Steps to replicate
requirements.in
pip-compile requirements.in
django-stubs
torequirements.in
pip-compile
django-stubs
fromrequirements.in
pip-compile
Why
pip-compile
in the 2nd step can't resolve there is a solution I manually added in the 3rd step?Why does the 6th step depend on an existing
requirements.txt
created in the 4th step?The text was updated successfully, but these errors were encountered: