-
-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: use pyenv to install compatible python version #3659
Comments
valid request, but... |
I had not considered the .bashrc part.... valid point there. Perhaps more of a FAQ thing then, because its one of those things that probably is going occur on and off half the time as Arch or similar distro will have a too new python frequently. |
perhaps you want to contribute and write a wiki article? |
Works without touching .bashrc Reference: https://docs.python.org/3.12/tutorial/venv.html As I understand that (really a noob here when it comes to scripts/programming and a noob on arch) it is a new feature making pyenv, python-virtualenv etc. obsolete. |
its doesn't make venv obsolete, that's exactly what its designed to do - when you activate venv, it will always use python executable that was used to create venv in the first place. but yes, that is one of ways to handle multiple python versions - manually pre-create venv before starting sdnext. anyhow, closing this feature request as pyenv cannot be added due to previously listed reasons. |
Feature description
This can be done manually currently but webui.sh or somthing should probably handle this so distros that update thier system python to a version that is too new can continue to work out of the box.
Version Platform Description
ArchLinux python 3.13.x is too new.
The text was updated successfully, but these errors were encountered: