A production (read: tagged) release of bioy will be downloaded by clinical pipelines which use dev/bootstrap.sh and expect that environments created using this script are static. By leaving the bioy source editable ("-e .") any changes made to the bioy source that originally produced that virtualenv (e.g, deleting the directory) will alter the bioy executable.
So just change "-e ." to "." and place it back in there when doing development.
When other proejcts list bioy as a requirement and it is NOT editable in that requirements.txt, the executable it produces won't depend on future edits to the source. So nevermind.
A production (read: tagged) release of bioy will be downloaded by clinical pipelines which use dev/bootstrap.sh and expect that environments created using this script are static. By leaving the bioy source editable ("-e .") any changes made to the bioy source that originally produced that virtualenv (e.g, deleting the directory) will alter the bioy executable.
So just change "-e ." to "." and place it back in there when doing development.