Closed CounterPillow closed 5 years ago
Nevermind, I found what went wrong.
Having a --user site install of pip-chill makes it pick up all site packages even if you install pip-chill in the virtualenv, probably because of $PATH weirdness. I checked the $PATH and the virtualenv pip should've been in there first, but apparently wasn't picked up until I uninstalled the site one, and only worked when I reactivated the venv in a new shell. Odd.
Description
pip-chill picks up site-packages even if the virtualenv it was installed and executed in specifies --no-site-packages.
What I Did
EDIT: Looks like
--no-site-packages
is the default now, so pip-chill installed in a virtualenv should never pick up packages from outside the virtualenv.