When running things in CI environments, one might not have access to write things outside of the workspace so quite often people resort to virtualenv. When venv is activated, there's VIRTUAL_ENV environment variable which tells the base path where things can be installed. If that variable is set (eg, venv is active), this patch uses that directory to download the webdriver and install the binary/link into correct location within the provided virtual env. Covers also windows side but its untested atm as i dont have access to windows box. Venv in windows doesnt install executables to "bin" but to "Scripts" folder ..
When running things in CI environments, one might not have access to write things outside of the workspace so quite often people resort to virtualenv. When venv is activated, there's VIRTUAL_ENV environment variable which tells the base path where things can be installed. If that variable is set (eg, venv is active), this patch uses that directory to download the webdriver and install the binary/link into correct location within the provided virtual env. Covers also windows side but its untested atm as i dont have access to windows box. Venv in windows doesnt install executables to "bin" but to "Scripts" folder ..