Open HemulenKnocks opened 3 years ago
I see this too, and perhaps it should be tracked separately, but I'm also seeing pip-sync -n
report that it'd uninstall/re-install.
At least the two are consistent :sweat_smile:
This code makes it seem like using #egg=name==version
would possibly alleviate the issue. It seems to work for me, so try that out!
However if I specify in my requirements.in
git+https://github.com/owner/repo@branchname#egg=name==1.0.0
, and pip-compile
, the requirements.txt
strip off the egg and version specifiers.
Might be worth filing a new issue for...
I have the same issue, but pip fails with the new backtracking resolver (no hash for the vcs dependency) as pip-tools recommends the MESSAGE_UNHASHED_PACKAGE
comment. So using links like https://github.com/jazzband/pip-tools/archive/SOMECOMMIT.zip
pip-sync re-installs packages.
pip-sync reinstalls VCS package even if it's installed(using ssh protocol)
Environment Versions
pip-tools==6.2.0
Steps to replicate
pip-sync requirements/cube.txt
Actual result