Jupyterhub upgrade for RHEL 8 images not available

Hi Team,

We have a jupyterhub 2.3.1 running on our rhel server, However we could not find any latest distributions available after 2.31 using pip to upgrade. Is this not released yet?

ERROR: Could not find a version that satisfies the requirement jupyterhub==3.0 (from versions: 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.4.1, 0.5.0, 0.6.0, 0.6.1, 0.7.0b1, 0.7.0, 0.7.1, 0.7.2, 0.8.0b1, 0.8.0b2, 0.8.0b3, 0.8.0b4, 0.8.0b5, 0.8.0rc1, 0.8.0rc2, 0.8.0, 0.8.1, 0.9.0b1, 0.9.0b2, 0.9.0b3, 0.9.0rc1, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 0.9.4, 0.9.5, 0.9.6, 1.0.0b1, 1.0.0b2, 1.0.0, 1.1.0b1, 1.1.0, 1.2.0b1, 1.2.0, 1.2.1, 1.2.2, 1.3.0, 1.4.0, 1.4.1, 1.4.2, 1.5.0, 1.5.1, 2.0.0b1, 2.0.0b2, 2.0.0b3, 2.0.0rc1, 2.0.0rc2, 2.0.0rc3, 2.0.0rc4, 2.0.0rc5, 2.0.0, 2.0.1, 2.0.2, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1) ERROR: No matching distribution found for jupyterhub==3.0
Appreciate your help.


JupyterHub official distributions are delivered in .tar.gz and .whl formats. Some of the folk responsible for those releases also help out on the mostly-automated conda-forge and dockerhub, as a number of jupyter services (like binder) rely heavily on those packages for the containers themselves, as well as user-serviceable packages inside them.

Beyond that, it’s basically not feasible to deliver bespoke packages for every flavor/version/arch combination, and furthermore, even if we did, they would not be in your distribution’s official channels.

As a paying customer, you might be able to raise the availability of these packages as an important issue, but as an open source community, we have enough on our hands getting official releases out the door.

Alternately, you could build your own RPMs, or find someone else that has.


Rereading again: perhaps you “just” need to upgrade python 3.7? If that’s not available from your package manager, there might be some optional tool (perhaps SCL) you can use to update to such a beast, or, failing that, use conda-forge.

And indeed, with a few months remaining before 3.7’s EOL, might as well go to something newer?


Thank you @bollwyvl . I’ll have the python upgraded to 3.7 and give a try again.

Looks like 3.7 isn’t much to write home about (and again, EOL in a few months), but you can go to 3.9 or 3.10:

A little sad, of course, as 3.11 would bring you actual performance upgrades instead of just walrus operators and new flavors of type hints, but That’s Enterprise Software :tm: for you.