py-tox: updated to 4.54.0
Features - 4.54.0
Declare the runtime dependencies of the tox.pytest plugin (pytest, devpi-process and pytest-mock) under a new testing extra, so plugin authors can pull them in via tox[testing] - by @gaborbernat.
Bug fixes - 4.54.0
Extend the generated TOML schema to cover every replace table form (env, ref, posargs, glob, if), including conditional replacements used inside commands. A guard test asserts the schema stays in sync with the loader implementation so future replace types cannot be added without a corresponding schema entry.
x86: use 0x40000010 cpuid leaf only on vmware and kvm
specifically, do not use it on nvmm.
these hypervisor cpuid leafs are basically hypervisor-specific.
(there was a proposal on commonizing these hypervisor leafs. [1]
but it doesn't seem agreed on.)
this cpuid leaf 0x40000010 was originally from vmware. although it
seems more common to use the GETHZ (45) hypercall instead these days.
kvm seems to implement it as well. (via qemu vmware-cpuid-freq)
i personally haven't tested this on either vmware or kvm.
for nvmm (netbsd), the leaf has been implemented in 2025. [2]
and then the lapic bit has been disabled in 2026. [3] that is,
we had no releases with it enabled. even if you are running the
-current version of nvmm, it's better to avoid using this leaf
[5 lines not shown]
nvmm: remove cpuid leaf 0x40000010
* given the lapic bit disabled, (PR/59424) [1]
this leaf doesn't seem to have much benefit anymore.
as nvmm is used in other platforms, (dragonfly bsd)
it's better to avoid guest ABI changes without clear benefits.
* I couldn't find any documenation about what RBX=0 means.
(vmware or kvm)
we can revisit this when/if someone comes up with a better
implementation. (probably userland-assisted one)
discussed on source-changes-d. [2]
reviewed by Taylor R Campbell.
[1] https://mail-index.netbsd.org/source-changes/2026/05/01/msg161786.html
[2] https://mail-index.netbsd.org/source-changes-d/2026/05/01/msg014654.html
gtk3: Make building wayland support conditional on GLAMOREGL on NetBSD.
While this seems... weird, at best, due to Historical Reasons
building libEGL was dependent on building the X server with GLAMOR
support in NetBSD. This is no longer true, but some problems linger
(e.g. with libepoxy in the base system).
As a special hack, for NetBSD with native X only, disable Wayland
support if the GLAMOR extension isn't enabled.
PR pkg/60295 x11/gtk3 does not build on NetBSD/macppc
libepoxy: Make EGL libs depend on EGL support rather than GLAMOR.
Build tested on sparc64, which has EGL but no GLAMOR x server.
If this is pulled up, it should happen before 11.0 is cut, since
it adds stuff to the ABI.
PR pkg/60295 x11/gtk3 does not build on NetBSD/macppc
ory-hydra: Add version 26.2.0
Ory Hydra is a server implementation of the OAuth 2.0 authorization framework
and the OpenID Connect Core 1.0. It follows cloud architecture best practices
and focuses on:
* OAuth 2.0 and OpenID Connect flows
* Token issuance and validation
* Client management
* Consent and login flow orchestration
* JWKS management
* Low latency and high throughput
py-oauthenticator: Add version 17.4.0
OAuth is a token based login mechanism that doesn't rely on a username and
password mapping. In order to use this login mechanism with JupyerHub the
login handlers need to be overridden. OAuthenticator overrides these handlers
for the common OAuth2 identity providers allowing them to be plugged in and
used with JupyterHub.
The following authentication services are supported through their own
authenticator: Auth0, Azure AD, Bitbucket, CILogon, FeiShu, GitHub, GitLab,
Globus, Google, MediaWiki, OpenShift.
There is also a GenericAuthenticator that can be configured with any OAuth 2.0
identity provider or can be used to create a new authenticator class when
py-jupyterhub: Add version 5.4.6
With JupyterHub you can create a multi-user Hub that spawns, manages, and
proxies multiple instances of the single-user Jupyter notebook server.
Project Jupyter created JupyterHub to support many users. The Hub can offer
notebook servers to a class of students, a corporate data science workgroup,
a scientific research project, or a high-performance computing group.
py-jupyterlab: updated to 4.5.7
4.5.7
Enhancements made
- Update default font family to honor macOS system-wide ui-monospace
Bugs fixed
- Video and Audio Content Providers: Fix JupyterLite support
- Fix notebook hang when dropping cells
- Fix Contextual Help keyboard shortcut reliability and menu Help functionality
- Fix focusing input element when opening a dialog from Command Palette
- Fix native context menu blocked even when context menu is suppressed
- Fix flaky toolbar item placement in popup
Maintenance and upkeep improvements
[7 lines not shown]
py-jupyter_server: updated to 2.18.2
2.18.2
Bugs fixed
- Fix saving user avatar URL
- Fix path resolution if `root_dir` is a filesystem root
Maintenance and upkeep improvements
- Add Zulip notification when a release is complete
- chore: update pre-commit hooks
py-django-tasks: updated to 0.12.0
0.12.0
Breaking changes
DB and RQ backends have been extracted into their own packages
Adresses 190 -- Failing task when exception raised for Import string
Align task status with Django SUCCESSFUL
Extract RQ and DB backends into separate packages
Remove metadata support
py-nltk: updated to 3.9.4
Version 3.9.4 2026-03-24
* Support Python 3.14
* Fix bug in Levenshtein distance when substitution_cost > 2
* Fix bug in Treebank detokeniser re quote ordering
* Fix bug in Jaro similarity for empty strings
* Several security enhancements
* Fix GHSA-rf74-v2fm-23pw: unbounded recursion in JSONTaggedDecoder
* Implement TextTiling vocabulary introduction method (Hearst 1997)
* Fix ALINE feature matrix errors and add comprehensive tests
* Support multiple VerbNet versions, fix longid/shortid regex for VerbNet ids
* Let downloader fallback to md5 when sha256 is unavailable
* Several other minor bugfixes and code cleanups
Version 3.9.3 2026-02-21
* Fix CVE-2025-14009: secure ZIP extraction in nltk.downloader
[5 lines not shown]
