You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: Unable to install using cmd prompt on windows 10 #303
Unable to install
Following the install instructions I get an error and I am unsure why ?.
The error obtained is "unable to install - error Can not combine '--user' and '--target' "
Yet I am not using --user so this doesn't make sense.
To Reproduce
Steps to reproduce the behavior:
Go to a 'cmd' prompt
Enter 'pip install pyenv-win --target %USERPROFILE%.pyenv'
Error displayed - ERROR: Can not combine '--user' and '--target'
Expected behavior
Pyenv-win to be installed
Additional context
It is windows 10 pro, username and so the contents of %USERPROFILE% does contain a space - wondered if this was a contributing factor.
Environment
I am using
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.19042 N/A Build 19042
and
Python 3.9.6
I encountered the same issue recently. I suggest you to use a virtual environment to install pyenv (it worked for me at least).
You just simply create a virtual environment using python -m venv /path/to/new/virtual/environment
Then activate the venv using Scripts\activate
Finally you can just simply pip install like the first time.
Note that using pip install in a virtual environment causes that you can only use the installed module within that same active environment.
Activity
mrlreable commentedon Oct 20, 2021
Hi @leegibbons6point6
I encountered the same issue recently. I suggest you to use a virtual environment to install pyenv (it worked for me at least).
You just simply create a virtual environment using
python -m venv /path/to/new/virtual/environmentThen activate the venv using
Scripts\activateFinally you can just simply pip install like the first time.
Note that using pip install in a virtual environment causes that you can only use the installed module within that same active environment.
Hope it helps!
jpmn commentedon Nov 17, 2021
I could circumvent this issue on Windows 10 by adding
--no-userat the end of thepipcommand in powershell.kirankotari commentedon May 30, 2022
@jpmn Hey you made my day. Let me add this is README