You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current prodenv/devenv simply do pip install -r requirements.txt to install dependencies.
This process will upgrade packages that were installed and need upgrading. It, however, does not remove packages that might have been legitimately previously installed, but are no longer needed.
There are cases where you might end up with unneeded packages in the virtualenv. For example:
you switch between development branches where the requirements change
the requirements are otherwise updated since you first install the virtualenv
Running pip-sync after installing the requirements should solve the problem, I think. It's perhaps a little bit complicated because we have separate recipes for prodenv and devenv.
The text was updated successfully, but these errors were encountered:
The current
prodenv
/devenv
simply dopip install -r requirements.txt
to install dependencies.This process will upgrade packages that were installed and need upgrading. It, however, does not remove packages that might have been legitimately previously installed, but are no longer needed.
There are cases where you might end up with unneeded packages in the virtualenv. For example:
Running
pip-sync
after installing the requirements should solve the problem, I think. It's perhaps a little bit complicated because we have separate recipes forprodenv
anddevenv
.The text was updated successfully, but these errors were encountered: