scripts/start.sh: line 13: venv/bin/activate: No such file or directory

[dikudeveloper]

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

As a new developer on-boarding to the project, you must clone the repo and set it up locally. To do this, you run, scripts/setup.sh, a Bash script that automates the process to reproduce it on your local machine. The script offers four options: option 1, creates a Python virtual environment for you using the famous virtualenv pip package, whereas option 4 skips virtual environment creation. In the subsequent parts of this write-up, I will limit the focus to what happens when you select option 4 assuming you have already created and activated your own virtual environment by another means. scripts/setup.sh with option 4 will complete and set you up successfully, however, a new problem is created. When you attempt to start the application locally through scripts/start.sh, It searches for a virtualenv virtual environment with the name venv within the project's root directory, and if it does not find it, returns an error.

scripts/start.sh: line 13: venv/bin/activate: No such file or directory

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via repl.

Steps described above

What is the expected behavior?

As a Developer who created their own local virtual environment outside the project, scripts/start.sh should start the application locally without any virtual environment error (assuming the Developer selected option 4 when running scripts/setup.sh). The script should also recognize virtual environment not named

venv

NB: You can drop a comment below for more clarification