If DMENV_VENV_OUTSIDE_PROJECT and working on foo/server and bar/server, both projects will share the same virtual env, leading to misbehavior regarding lock generation ...
One solution would be to do what pipenv does, and add a hash of the full path of the project to the cache patch
If
DMENV_VENV_OUTSIDE_PROJECTand working onfoo/serverandbar/server, both projects will share the same virtual env, leading to misbehavior regarding lock generation ...One solution would be to do what pipenv does, and add a hash of the full path of the project to the cache patch