Repository navigation
bug: pyenv install is launching a UI window, when it should be a silent install #396
Description
Describe the bug
pyenv install 3.10.4 is launching a UI window for the user to click thru and finish the install
To Reproduce
Steps to reproduce the behavior:
- Install pyenv - https://github.com/pyenv-win/pyenv-win#installation
- Verify pyenv is properly installed.
pyenv --version=3.0- Question: I am noticing 2.64.11 is the latest release at this time, not sure why/how I am getting
3.0. Any ideas?
- Question: I am noticing 2.64.11 is the latest release at this time, not sure why/how I am getting
- Try to install version of python.
3.10.4for example -pyenv install 3.10.4, and notice the UI popup - The process will be stuck until someone clicks thru the UI. Not ideal for automation on build machines
Expected behavior
- Install should be silent and should not expect the user to click thru the UI
Desktop (please complete the following information):
- OS: Windows 10
- Tools used -
cmd prompt
Activity
kirankotari commentedon Jun 6, 2022
Yes, this is know issue from latest python versions i.e 3.10.x and latest 3.9.x versions.
kirankotari commentedon Jun 6, 2022
If anyone can debug why this is happening for these version that will be help full, please let us know the root cause of it, we always welcome you to contribute to this repo.
Thanks in Advance.
scorpion35 commentedon Jun 6, 2022
Also noticing a different UI some other times
kirankotari commentedon Jun 6, 2022
Yes, we know about this too, Noted.
danhje commentedon Jun 16, 2022
Duplicate of #373. Not super happy with the solution suggested over there though, I have scripts that expect
pyenv install x.y.zto work, and don't want to have to update them all to (conditionally) apply the--quietflag. Is there a good reason to not make that the default behavior?kirankotari commentedon Jun 16, 2022
The older versions are installing quietly without the flag. This is due to latest python exe versions.
Why we are not adding
--quiteby default?The enterprise developer based on company rules they will get a popup to get admin rights on installation, if i use
--quiteby default, these developer won't be able to use pyenv-win.Darsstar commentedon Jul 19, 2022
It is fixed on the master branch. (see #410) If you want to clean up your PC you should uninstall via WIndow's "Add or remove Programs" system settings page and pyenv uninstall after that. re-installing should now work as you were used to.
issam-seghir commentedon Aug 3, 2022
the same problem here but with update the last version of python installed with pyenv and not with system version
pyenv 2.64.11Darsstar commentedon Aug 3, 2022
Please upgrade to 3.1 or higher
issam-seghir commentedon Aug 3, 2022
i installed the pyenv-win with chocoletey and this the last version on it
2.64.11kirankotari commentedon Aug 3, 2022
We recommend to use PowerShell with right permissions. It's a single command to Install. This way you can get latest code all the time. We haven't automated chocolatey to take latest code automatically.
Link: https://github.com/pyenv-win/pyenv-win#power-shell
issam-seghir commentedon Aug 3, 2022
so before that, i need to uninstall the chocolatey version, and what about my python versions , do i need to reinstall all of the themes ?
kirankotari commentedon Aug 3, 2022
No need to uninstall pyenv-win, the Powershell command needs to override existing version. This must not disturb your existing python AFAIK, but we haven't test this scenario which is OOB. You can take a backup of python versions which are in following path
%USERPROFILE%/.pyenv/pyenv-win/versionsJIC (Just in case).issam-seghir commentedon Aug 3, 2022
error when installing with PowerShell because i don't have the permission
so I use the command:
⚡ 🚀 Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachinebut ended with another error !! (i run PowerShell with administrator permission )
Darsstar commentedon Aug 3, 2022
Try
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process -Force