@leuko -- works fine for me. python-pamela is a dependency, and the virtual environment is created with --system-site-packages so it should use any packages you have installed on your system (unless they are explicitly reinstalled into the venv). python-pamela is an AUR package; the first thing to check would be you have built it for the system version of Python (pacman -Ql python-pamela should show it installing files in /usr/lib/python3.12).
Search Criteria
Package Details: jupyterhub 5.2.1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/jupyterhub.git (read-only, click to copy) |
|---|---|
| Package Base: | jupyterhub |
| Description: | Multi-user server for Jupyter notebooks |
| Upstream URL: | https://jupyter.org/hub |
| Licenses: | BSD-3-Clause |
| Submitter: | xantares |
| Maintainer: | bcb |
| Last Packager: | bcb |
| Votes: | 9 |
| Popularity: | 0.000000 |
| First Submitted: | 2015-03-12 14:00 (UTC) |
| Last Updated: | 2024-11-21 15:30 (UTC) |
Dependencies (38)
- ipython (ipython-gitAUR)
- nodejs-configurable-http-proxyAUR
- python-alembic
- python-certipyAUR
- python-dateutil
- python-jinja
- python-jupyter-events
- python-oauthlib
- python-packaging
- python-pamelaAUR
- python-prometheus_client
- python-psutil
- python-pydantic
- python-requests
- python-sqlalchemy (python-sqlalchemy1.3AUR, python-sqlalchemy-gitAUR, python-sqlalchemy1.4)
- python-tornado
- python-traitlets
- npm (corepackerAUR, python-nodejs-wheelAUR) (make)
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- python-setuptools (make)
- python-setuptools-scm (make)
- python-wheel (make)
- yarn (yarn-pnpm-corepackAUR, corepackerAUR, yarn-berryAUR) (make)
- jupyter-notebook (check)
- python-beautifulsoup4 (check)
- python-cryptography (check)
- python-jsonschema (check)
- python-playwright (python-playwright-gitAUR) (check)
- python-pytest (check)
- python-pytest-asyncio (check)
- python-pytest-rerunfailures (check)
- python-requests-mock (check)
- jupyter-notebook (optional) – standard notebook server
- jupyterlab (jupyterlab-3) (optional) – to use the JupyterLab interface
- python-cryptography (optional) – encrypt authentication state
- python-pycurl (optional) – improved HTTP performance
- python-statsdAUR (python-statsd-gitAUR) (optional) – send metrics to a StatsD server
Required by (7)
Sources (3)
bcb commented on 2024-08-24 07:57 (UTC)
leuko commented on 2024-07-31 09:08 (UTC)
During test:
E ModuleNotFoundError: No module named 'pamela'
Probably pamela is not present in the test-env
bcb commented on 2024-06-29 11:49 (UTC)
The upgrade to 5.0.0 has a substantial increase in size (14 MB -> 37MB). This is mostly in the static files for the bootstrap CSS framework and the fontawesome fonts. I assume this is related to the fact the release includes an upgrade of bootstrap to v5 (pull request 4774).
UlyssesZhan commented on 2024-04-29 08:24 (UTC)
@lahwaacz Thank you for the note! I wasn't aware of this. After yay -S $(pacman -Qoq /usr/lib/python3.11), everything seems fine now.
lahwaacz commented on 2024-04-29 08:13 (UTC)
@UlyssesZhan You have probably not rebuilt python-jupyter_telemetry for Python 3.12 yet.
UlyssesZhan commented on 2024-04-29 08:10 (UTC)
4.1.5 build fails with ModuleNotFoundError: No module named 'jupyter_telemetry'.
bcb commented on 2024-03-20 14:38 (UTC)
I have just pushed an update to 4.1.0.
As reported in previous comments, the tests do not work with the current version of python-pytest-asyncio in the repositories; the JupyterHub CI / pyproject.toml has this pinned to < 0.23. As this is only required for check() (not to run JupyterHub) and the tests were already being run in a temporary virtual environment, I have modified check() to install a compatible version of that test plugin into the test virtual environment. The tests run successfully in a clean chroot for me, hopefully they work elsewhere too!
UlyssesZhan commented on 2024-03-01 23:08 (UTC) (edited on 2024-03-03 07:28 (UTC) by UlyssesZhan)
Tests are failing on a clean env. After forcing it to be installed by adding --nocheck flag, I find it seeming to work fine, though.
iyanmv commented on 2024-02-14 10:30 (UTC)
Most tests fail for me to run on a clean env. Probably related to this: https://github.com/pytest-dev/pytest-asyncio/issues/718
tinux commented on 2023-08-16 07:40 (UTC)
@bcb Thanks for the info. I should have realized myself that this had been archived.
Thanks also for the package update! Now the previously described issue is solved and /lab starts directly as expected. <3
Pinned Comments
bcb commented on 2021-12-05 16:27 (UTC)
Note that version upgrades may require you to upgrade the database before the new version will start. Always check the documentation, in particular the changelog before upgrading.