@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.
Search Criteria
Package Details: jupyterhub 4.1.5-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.000002 |
First Submitted: | 2015-03-12 14:00 (UTC) |
Last Updated: | 2024-04-14 11:23 (UTC) |
Dependencies (33)
- ipython (ipython-gitAUR)
- nodejs-configurable-http-proxyAUR
- python-alembic
- python-async_generatorAUR
- python-certipyAUR
- python-entrypoints
- python-jinja
- python-jsonschema
- python-jupyter_telemetryAUR
- python-oauthlib
- python-packaging
- python-pamelaAUR
- python-prometheus_client
- python-requests
- python-sqlalchemy (python-sqlalchemy-gitAUR, python-sqlalchemy1.3AUR)
- python-tornado
- python-traitlets
- npm (corepackerAUR) (make)
- python-build (make)
- python-installer (python-installer-gitAUR) (make)
- Show 13 more dependencies...
Required by (6)
Sources (3)
UlyssesZhan commented on 2024-04-29 08:24 (UTC)
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
lahwaacz commented on 2023-08-12 10:32 (UTC)
@bcb Thanks for updating the package, version 4.0.2 built fine for me without any test failure.
bcb commented on 2023-08-12 10:20 (UTC)
@tinux - https://github.com/jupyterhub/jupyterlab-hub has been archived for more than 4 years; the deprecation message says equivalent functionality is in JupyterLab itself. I would guess that it no longer works properly with the latest versions of other projects, and your best move is probably to migrate away from it.
bcb commented on 2023-08-12 10:17 (UTC)
@lahwaacz -- thanks for the information re. yarn, I have added it as a makedepend for 4.0.2 and /usr/share/jupyterhub/static/js/admin-react.js
is in the package. test_token_page
passes for me in a clean chroot, I am not sure if it has been fixed with 4.0.2 or if this is another intermittent failure.
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.