www/py-asgiref 3.12.1 NetBSD

3.13.0 (2026-10-23) * It is now possible to nest ``ThreadSensitiveContext`` by providing an explicit ``executor`` for thread-sensitive tasks. This enables moving a block of such work away from the parent context's shared worker. The provided executor must run work sequentially and on a single thread, as per ``ThreadPoolExecutor(max_workers=1)``, and the calling code is responsible for managing the executor's lifecycle. See the README for more details. * ``Local`` attribute access is now 2-3x faster. ``Local(...)`` now uses one of two internal specialisations, selected by ``thread_critical``, instead of checking the mode on every access. As a result ``Local`` is now marked ``@final`` and raises ``TypeError`` if …

3.12.1 (2026-07-14) * Restored the previous SyncToAsync.__call__ internal code shape, which was relied on by some APM services. Note, this change was available whilst maintaining the underlying fix. It does not constitute an API stability promise. Ideally APMs are *not* monkey patching internal APIs, and future changes will be made here if needed. 3.12.0 (2026-07-14) * ``AsyncToSync`` no longer captures the running event loop on instantiation. This resolves a series of deadlocks that users experienced after asgiref 3.9.0, particularly with pytest-asyncio. pytest-asyncio stops the event loop between tests, and long-running unawaited futures could find themselves trying to schedule work onto a stopped loop, and so would never complete. Ideally, code …