Using virtual environments

• Task 0-RUN Get app running and view it in a browser

If you have other Python projects installed which are dependent on specific library versions (i.e. have a requirements.txt file included), we recommend that you use a Python virtual environment for installing the Buggy Editor dependencies to avoid any conficts. Instructions for installation are show below. Note that you may need to activate your virtual environment each time you open a new Terminal in VSCode.

Instructions for Unix (Mac) users:

• Open a new Terminal in VSCode using the menu Terminal -> New Terminal. Run pwd and confirm you are in the buggy-editor-main folder, if not, change directory into it.

• Run python3 -m venv buggy-env and select "Yes" when the popup says "We noted a new environment has been created. Do you want to select it for the workspace folder?". You now have a virtual environment called buggy-env.

• Run source buggy-env/bin/activate - this will activate the new virtual environment.

• To confirm you are using the virtual environment, run which python. This should return a directory ending in buggy-editor-main/buggy-env/bin/python.

Instructions for Windows users:

• Open a new Powershell Terminal in VSCode using the menu Terminal -> New Terminal. Run pwd and confirm you are in the buggy-editor-main folder, if not, change directory into it.

• Run python -m venv buggy-env and if it appears, select "Yes" when the popup says "We noted a new environment has been created. Do you want to select it for the workspace folder?". You now have a virtual environment called buggy-env.

• Run buggy-env\Scripts\activate - this will activate the new virtual environment.

• To confirm you are using the virtual environment, run where python. This should return a directory ending in buggy-editor-main/buggy-env/bin/python.