#143 switched over to using the pixi package manager, which is advantageous because it supports both the pyproject.toml file and the conda-forge repository. conda-forge is especially desirable because it provides some binary packages for dependencies which would otherwise require compilation using GCC when installed from PyPi #122. The use of pixi facilitates building multi-architectural images #145.

However, all of this extra effort is necessary only to support one entirely unused subdependency.

python-keystoneclient depends on psutil, which does not provide binary wheels on PyPI, whereas conda-forge does provide binary packages for it.

Despite the large effort already spent on adding OpenStack support into ChRIS components, we have never used OpenStack in production. Even if we were to use OpenStack Swift, it would be advantageous to use the vendor-neutral S3 protocol to access Swift instead of the Swift client library.

Conclusion: removing the dependency on python-keystoneclient would allow us to switch from pixi to the more mainstream uv package manager.