Closed franciscosucre closed 6 years ago
Hi @franciscosucre will check it this afternoon (France time) br
You're right, this is a bug. The script will search the python path not the python executable.
mkvirtualenv -Python c:\Python27amd64\ -Name QueTal
will work. Remove python.exe
at the end of the command.
It does not work on my Windows 10
- System using PowerShell
.
I also get the error:
ERROR: The path to access to python doesn't exist. Python directory = ...
The entire CLI output:
PS C:\Users\username\Projects\project> (gcm python).Path
C:\Users\username\.pyenv\pyenv-win\shims\python.bat
PS C:\Users\username\Projects\project> mkvirtualenv -Python C:\Users\username\.pyenv\pyenv-win\shims -Name MyNewEnv
ERROR: The path to access to python doesn't exist. Python directory = C:\Users\username\.pyenv\pyenv-win\shims
PS C:\Users\username\Projects\project> ls C:\Users\username\.pyenv\pyenv-win\shims\
Directory: C:\Users\username\.pyenv\pyenv-win\shims
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 26.04.2021 16:29 51 easy_install
-a---- 26.04.2021 16:29 51 easy_install-3.9
-a---- 26.04.2021 16:29 66 easy_install-3.9.bat
-a---- 26.04.2021 16:29 66 easy_install.bat
-a---- 26.04.2021 16:29 51 pip
-a---- 26.04.2021 16:29 66 pip.bat
-a---- 26.04.2021 16:29 51 pip3
-a---- 26.04.2021 16:29 51 pip3.9
-a---- 26.04.2021 16:29 66 pip3.9.bat
-a---- 26.04.2021 16:29 66 pip3.bat
-a---- 26.04.2021 16:29 43 python
-a---- 26.04.2021 16:29 58 python.bat
-a---- 26.04.2021 16:29 43 python3
-a---- 26.04.2021 16:29 43 python3.9
-a---- 26.04.2021 16:29 58 python3.9.bat
-a---- 26.04.2021 16:29 58 python3.bat
-a---- 26.04.2021 16:29 43 python39
-a---- 26.04.2021 16:29 58 python39.bat
-a---- 26.04.2021 16:29 43 pythonw
-a---- 26.04.2021 16:29 58 pythonw.bat
-a---- 26.04.2021 16:29 43 pythonw3
-a---- 26.04.2021 16:29 43 pythonw3.9
-a---- 26.04.2021 16:29 58 pythonw3.9.bat
-a---- 26.04.2021 16:29 58 pythonw3.bat
-a---- 26.04.2021 16:29 43 pythonw39
-a---- 26.04.2021 16:29 58 pythonw39.bat
Hi @AndreasLuckert VirtualEnvWrapper for Powershell wasn't created to deal with PyEnv but with pure Python installation.
If you still have the problelm, you should create a new issue because this issue is closed.
Regards
Hey man sorry to bother you but i get another error while making use of mkvirtual env
By the way, if would be awesome if the wraper searched for the virtualenvs in the path so one could just give python.exe to the -Python keyword.