Release v8.6

This version brings support for...

• the CRITICAL log level
• the exception method being called through structlog's BoundLogger (bugfix!)
• structlog related verifications in classic test cases.

Release v8.5

Main change in this release is the refactor of how Sequences are detected/matched, to fix some issues (its functionality didn't change, it's just more robust now).

Release v8.4

(from 8.2)

• Support crossing simultaneous stdlib/structlog usage.
• Default to regex when structlog kwarg is bytes.

Release v8.2

Support the case of codebase using multiple logging/handlers at the same time.

Release v8.1

Fix for using structlogs with named loggers.

v8

The version 8 of logassert brings support for the structlog library. Yes, now you can use the whole power of logassert when using structlog as a logger. As it's the first release with this support we may tune it or make it better with future small adjustments, please open issues or contact me if you work with it and have ideas/problems to solve, thanks!

There is also small administrative enhancements: better README (and documentation in Read The Docs), the CI uses modern Pythons, better tested badge, etc.

Release v7

• Teardown the handler after test run

Release 6

• Simple way to check that nothing was logged (on any level or a specific one):

    assert NOTHING in logs.debug

• Helper to check that several lines were logged one after the other:

    assert Sequence(
        "Got 1 error and \d+ warnings:",
        Exact("  error: bar"),
    ) in logs.debug

• Show proper message when "not in" assertion is used (thanks Diego Mascialino)