have an option , while developing a driver , to not load the virtual environment every time

Hi Yoav,

I think the pain you are raising here is the fact that it takes a long time to create a new virtual environment and that we are creating a new virtual environment every time you upload a new driver to cloudshell.

Disabling the virtual environment creation isn't a good practice since it's very error prone and may lead to missing dependency or a wrong virtual environment for your driver, so it will appear working or not while it's not actually true to the production environment.

We can look into speeding up the process for spinning up virtual environment or only creating a new one if the driver requirements have changes.

Hi Dan,

During the normal life of a shell , the virtual environment creation does not happen that often. but when developing , it happens multiple times, even if no changes were made to the requirements.

creating a new environment on changed requirement should be good enough. if I do change the requirements , I will probably need a new venv anyway.

thanks,

Yoav

I believe by default, virtual environment creation should remain.

Adding a 'dev' flag to the shellfoundry command to disable automatic venv creation could be useful.

Natti

Also if there is a Dev Flag, then the system should automatically take down previous venv, so they aren't just hanging out waiting for a restart.

@kimo if there is a dev flag, that should mean leave the existing venv alone. Normally a new venv is generated everytime you upload shell as this increments internal "version" counter and server has no way of knowing if requirements changed so it creates new venv. If as a developer you know the version did not change, you pass the "dev=True" flag and you can use the existing venv without a rebuild