Change hooks control (deny_all_hooks_but / allow_all_hooks_but) to be more predictable Prior to this, if one execute code like: with cnx.hooks.deny_all_hooks_but('metadata'): with cnx.hooks.deny_all_hooks_but(): # mycode 'metadata' hooks will be activated anyway in the inner block, which is rather unexpected (of course in real life you only see the latest hooks control statement, the former being higher in the call stack). This is due to the underlying usage of old `enable_hook_categories` / `disable_hook_categories` methods, which were introduced much before the now official context manager based API (with `cnx.[deny|all]_all_hooks_but(...)`). To move on, this patch drop the two legacy methods, rename and privatize related internal state on the connection (`hooks_mode` becomes `_hooks_mode`, `disabled_hook_cats` and `enabled_hook_cats` become `_hooks_categories`) and reimplement the `_hooks_control` context manager to simply update them. See the added unit test for details.

     1

:mod:`cubicweb.pyramid`

     2

=======================

     3

     4

.. automodule:: cubicweb.pyramid

     5

     6

    .. autofunction:: make_cubicweb_application

     7

     8

    .. autofunction:: wsgi_application_from_cwconfig

     9

    10

    .. autofunction:: wsgi_application

    11

    12

.. toctree::

    13

    :maxdepth: 1

    14

    :glob:

    15

    16

    pyramid/*

    17