Python: Installed in C:\Users\sukil\AppData\local\programs\python\python39 (and \python39-32 )
Vex and virtualenv: Installed user-wide, in C:\users\sukil\appData\roaming\programs\python\python39
When Vex tries to find virtualenv, it uses sys.executable, and appends scripts\virtualenv to its dirname, which results in an error.
Using sys.argv[0] in place of sys.executable and removing the line which says "scripts" solves my problem, but I'm not sure if it's a general enough solution or if anything will break (I think it is, since I cannot run vex indirectly with python -m vex).
I have the following setuversion p:
When Vex tries to find virtualenv, it uses
sys.executable, and appendsscripts\virtualenvto itsdirname, which results in an error.Using
sys.argv[0]in place ofsys.executableand removing the line which says"scripts"solves my problem, but I'm not sure if it's a general enough solution or if anything will break (I think it is, since I cannot run vex indirectly withpython -m vex).