Upgrade to a newer Python version documentation not functional for python3.10.x #824
Comments
|
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
bigpick
changed the title
|
In trying a bunch of different stuff, it seems like maybe just doing a sudo env "PATH=$PATH" pip install <reqs_without_conda>at the end (vs. just the documented |
|
Doing the following seems to have worked now; Python versions show 3.10.x ( source /opt/tljh/user/bin/activate
conda env export --json | jq -r '.dependencies[] | objects | .pip[]' > pip_reqs_from_conda.txt
sudo env PATH=${PATH} conda update --all # has confirmation prompt
sudo env PATH=${PATH} conda install python=3.10 # has confirmation prompt
sudo env "PATH=$PATH" pip install -r pip_reqs_from_conda.txtWill open a PR in a bit |
|
Your solution fails for me at the python 3.10 installation step with the following output: |
|
Same problem here with a JupterHub installed on an Azure VM with Linux Server 22.04 LTS. |
|
I tried figuring out why it installs python 3.9 in the user environment and got as far as this part of the installer code: Maybe setting different versions in there would lead to python 3.10. In the end, I decided to work around the problem by simply creating a new conda/jupyter environment with python 3.10. I suspect that the Running See also here: https://discourse.jupyter.org/t/how-can-i-specify-the-python-version-to-use-install-system-and-hub-is-3-10-while-user-is-3-9/15763 |
|
I just discovered there is a pull request for allowing specifying the python version on install: #784 |
|
None of these methods are working for me. Is there no straightforward way to update the user environment to Python 3.10? Is this a compatibility issue? |
|
I am currently testing some code allowing you to use a different version of mambaforge than the one hard-coded in https://github.com/jupyterhub/the-littlest-jupyterhub/blob/main/tljh/installer.py#L156. This enabled me to get python 3.10 out of the box by pulling the latest mambaforge. So far, I have no complaints from my users. The code is at https://github.com/kiwifb/the-littlest-jupyterhub/tree/mambaforge_env |
Bug description
Following the instructions in the documentation on how to Upgrade to a newer Python version, no users are able to create a new server, admin or not.
The default TLJH setup works fine, and I've been able to run it as is on a manual setup w/HTTPs+etc. just fine. However, attempting to upgrade the python version for users to 3.10.x, the server functionality is entirely broken.
Expected behaviour
Following the steps in the documentation should result in the desired state (upgraded python version) with a still functional hub setup.
Actual behaviour
The hub fails to create any new user server's after the doc steps have been following (slightly modified so they actually work, bc as they're written now are also broken; the
... @ file:///...conda packages all get removed and are thus broken when the lastpip install ...is attempted. I've tried simply removing those packages entirely, just removing the@ ...and also doingpip list --format=freezeand using that package, none of which seem to have any effect on the problem here, which is the hub being unable to create any new user servers after upgrade.journalctllogs (see below logs section) for the user's process seems to show it complaining about ajupyterhubpackage missing, but if I manually check the script that it say's is being invoked, it seems to show that is installed, and that the python at the script's shebang can even import it itself?:cat /opt/tljh/hub/bin/jupyterhub-singleuser #!/opt/tljh/hub/bin/python ...and
How to reproduce
Your personal set up
Full environment
from inside venv, AFTER upgrade
Configuration
Logs
For
journalctl -u jupyterhubwhen trying to start a user's server AFTER upgrade:For
journalctl -u testoperator.service:The text was updated successfully, but these errors were encountered: