-
-
Notifications
You must be signed in to change notification settings - Fork 615
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-sync does not upgrade existing packages #1021
Comments
Hello @tekumara Thanks for the issue. I can't reproduce it locally. Perhaps, you run the pip-sync installed in other virtual environments, where the packages are already upgraded. Could you check the python, pip and pip-sync paths by running the following commands?
Thanks! |
Ah.. So I installed pip-tools using pipx into its own virtualenv because I didn't want to pollute my project's requirements.txt with pip-tools. This is what I have
Is it possible to make pip-sync work when installed in its own virtualenv? |
I see. You don't have to put pip-tools to requirements.txt, but make sure that pip-tools installed in the virtual environment. |
Unfortunately not. pip-tools must be installed in the virtual environment. |
Gotcha. That wasn't intuitive to me. Would you accept a PR to mention this in README.md? |
Great idea. PR is highly welcomed! |
Environment Versions
3.6.9
pip 19.3.1
pip-sync, version 4.3.0
Steps to replicate
Expected result
That the following up/downgrades would occur:
boto3 1.10.44 -> 1.10.43
pyjq 2.3.1 > 2.4.0
pytoml 0.1.20 -> 0.1.21
Actual result
No up/downgrades occurred.
The text was updated successfully, but these errors were encountered: