Virtualenv with auto restart

[JohnnyCoffee]

Is there any way to leave virtualenv in autorestart mode so that you don't have to use the (deactivate) and (activate) command to restart it ?

[Larz60+]

It would be the chore of your IDE to do this.

Using VSCode, If you have selected your virtual environment as the python interpreter (ctrl-shift-P --> python:select interpreter), then whenever you select new terminal from menu, it will open with the virtual environment active.

However If I close a folder that has a terminal window in which the virtual environment has been activated, exit VSCode, and then re-start, the terminal window appears, but not with virtual environment activated. I haven't been able to figure this one out.

[JohnnyCoffee]

It would be the chore of your IDE to do this.

Using VSCode, If you have selected your virtual environment as the python interpreter (ctrl-shift-P --> python:select interpreter), then whenever you select new terminal from menu, it will open with the virtual environment active.

However If I close a folder that has a terminal window in which the virtual environment has been activated, exit VSCode, and then re-start, the terminal window appears, but not with virtual environment activated. I haven't been able to figure this one out.

What I really need after deploying the application to the server is to leave virtualenv always activate (running) because as soon as I exit and close the terminal, virtualenv ends the session leaving virtualenv (off) and the application stops working ?

[ndc85430]

Is it the best solution to use a virtual environment? You could run the app in a Docker container to achieve isolation.