It looks as though the websockify that is provided as an RPM from the OnDemand yum/dnf repository has /usr/bin/python2 hard coded as the python interpreter.
We are doing and upgrade to RH 8, python 2 is no longer a required package, and as part of the decade-long attempt to wean people from python version 2, which I think is no longer supported, are there any plans to convert that to use /usr/bin/python3?
That appears to be the only thing that requires us to install
We are installing Open OnDemand v2.0.20, and I checked what was in the RH8 OnDemand repository from which we are getting it.
It looks like there are websockify RPMs out there for Python 3, but I do not know whether there are still issues with things like TurboVNC, which there might have been at one time.
It would be nice not to have to install python 2 just for the websockify from OnDemand.
This is likely a sysadmin preference so can vary from site to site but mixing pip and RPM installs can sometimes lead to problems where suddenly you have files that RPMs think they manage but really they are coming from pip. This is much less of an issue with RHEL8+ since they use a different install of python for the package manager and I think the websockify dependencies are pretty minimal so shouldn’t pull in too much except maybe setuptools which could conflict with RPMs.
UAz has not used the websockify RPM for historical reasons (our OOD genesis preceded the OOD repo). Currently, I’m running websockify via a wrapper script referenced in the cluster YAML file “script_wrapper” section.
That wrapper uses our python3 module which has had ‘pip3 install websockify’ done to it. Haven’t seen any problems with that