pytest-loguru
A pytest plugin to add support for loguru to pytest's caplog fixture.
You can install it from pypi with:
pip install pytest-loguru
and from conda-forge with:
conda install -c conda-forge pytest-loguru
Usage
Once installed, the plugin is registered automatically through pytest's
pytest11 entry point, so no import or configuration is needed. Messages
logged with loguru show up in caplog just like standard logging records,
and caplog.at_level / caplog.set_level filter them as usual:
import logging
from loguru import logger
def test_logs(caplog):
logger.warning("something happened")
assert "something happened" in caplog.text
def test_levels(caplog):
with caplog.at_level(logging.ERROR):
logger.info("ignored")
logger.error("kept")
assert caplog.messages == ["kept"]
Loguru records also reach pytest's other log handlers, in every test
whether or not it requests caplog: they appear under "Captured log call"
when a test fails, and in the live log when log_cli is enabled. Each
handler's level (log_level, log_cli_level) filters them as it does
standard logging records. Loguru's own sinks, such as the default stderr
one, are left alone.
Note that coverage is 100% but the coverage tool is confused by the fixture decorator.
Development
Environment
Development is currently done using Python 3.12. The environment can be created with:
uv sync
This creates a .venv folder with the versions specified in the project's uv.lock file.
Pre-commit
pre-commit will be installed when syncing uv. It is run every time you make a git commit if you call it like this:
pre-commit install
With pre-commit, all code is formatted according to ruff guidelines.
To check if your changes pass pre-commit without committing, run:
pre-commit run --all-files
Packages
uv is used for package management. If you've introduced a new package to the source code (i.e. anywhere in src/), please add it to the project.dependencies section of pyproject.toml with any known version constraints.
To add packages required only for testing or development, add them to the [dependency-groups] section in pyproject.toml.
Any changes to the dependencies will be automatically reflected in uv.lock with pre-commit, but you can re-generate the file without committing by executing:
uv lock --upgrade
Project
uv is used for project management. The project can be built using:
uv build
Linting and syntax checking can be run with:
uv run ruff format --check
uv run ruff check
Tests can be executed using:
uv run pytest
Coverage must stay at 100%. Measure it with coverage run rather than
pytest-cov, which starts too late to see the plugin's import:
uv run coverage run -m pytest
uv run coverage report
Metadata
Release files for pytest-loguru 0.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pytest_loguru-0.4.2.tar.gz | 62.3 kB | Without provenance | Details for pytest_loguru-0.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pytest_loguru-0.4.2-py3-none-any.whl | Python 3 | none | any | Details for pytest_loguru-0.4.2-py3-none-any.whl |
Total release size: 68.1 kB
Release files / pytest_loguru-0.4.2.tar.gz
| Download URL | pytest_loguru-0.4.2.tar.gz |
|---|---|
| Size | 62.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ad365b4149a99e6cc26cde01d225e776617bffbce3af3fc6d90fdb9fb34c9302
|
|
BLAKE2b-256 checksum How to use checksums |
2683824ffbe077f06cff80a314ade8d0dff03864702a50275ad58e88a9cbaee9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / pytest_loguru-0.4.2-py3-none-any.whl
| Download URL | pytest_loguru-0.4.2-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
282bba4c27c72e9cdea0680fb455642919649bf7f3a110723275cbfe3c40a44b
|
|
BLAKE2b-256 checksum How to use checksums |
4a41083ae640f6942505c7c4093a2317faeedbe7de1d2558e9932a54aa40044a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for pytest-loguru 0.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.