pico-testing 0.1.0__tar.gz

pico_testing-0.1.0/.coveragerc

@@ -0,0 +1,18 @@
+[run]
+branch = True
+source =
+    pico_testing
+omit =
+    */_version.py
+
+[paths]
+pico_testing =
+    src/pico_testing
+    .tox/*/lib/*/site-packages/pico_testing
+    .tox/*/site-packages/pico_testing
+    */site-packages/pico_testing
+
+[report]
+show_missing = True
+omit =
+    */_version.py

pico_testing-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,24 @@
+name: Bug Report
+description: Report a bug
+labels: [bug]
+body:
+  - type: textarea
+    id: description
+    attributes: { label: Description }
+    validations: { required: true }
+  - type: textarea
+    id: steps
+    attributes: { label: Steps to Reproduce, render: python }
+    validations: { required: true }
+  - type: textarea
+    id: expected
+    attributes: { label: Expected Behavior }
+    validations: { required: true }
+  - type: input
+    id: version
+    attributes: { label: Package Version }
+    validations: { required: true }
+  - type: input
+    id: python
+    attributes: { label: Python Version }
+    validations: { required: true }

pico_testing-0.1.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,15 @@
+name: Feature Request
+description: Suggest an improvement
+labels: [enhancement]
+body:
+  - type: textarea
+    id: problem
+    attributes: { label: Problem }
+    validations: { required: true }
+  - type: textarea
+    id: solution
+    attributes: { label: Proposed Solution }
+    validations: { required: true }
+  - type: textarea
+    id: alternatives
+    attributes: { label: Alternatives Considered }

pico_testing-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+## Summary
+
+## Changes
+
+-
+
+## Checklist
+
+- [ ] Tests pass (`pytest tests/ -v`)
+- [ ] Linting passes (`ruff check src/ tests/`)
+- [ ] CHANGELOG.md updated (if user-facing)
+- [ ] No new runtime dependencies
+- [ ] Single-line commit messages

pico_testing-0.1.0/.github/dependabot.yml

@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"

pico_testing-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,69 @@
+name: CI
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.11"
+      - run: pip install ruff
+      - run: ruff check src/ tests/
+      - run: ruff format --check src/ tests/
+
+  tests:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-python@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+      - run: pip install tox
+      - name: Run tests with coverage
+        env:
+          SETUPTOOLS_SCM_PRETEND_VERSION: "0.1.0"
+        run: |
+          tox -e cov
+          mv .coverage .coverage.${{ matrix.python-version }}
+      - uses: actions/upload-artifact@v7
+        with:
+          name: coverage-${{ matrix.python-version }}
+          path: .coverage.${{ matrix.python-version }}
+          include-hidden-files: true
+          if-no-files-found: error
+
+  coverage:
+    needs: tests
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: actions/setup-python@v6
+        with:
+          python-version: "3.12"
+      - uses: actions/download-artifact@v8
+        with:
+          path: coverage-reports
+      - name: Combine and upload
+        run: |
+          pip install coverage
+          files=$(find coverage-reports -type f -name ".coverage.*")
+          if [ -z "$files" ]; then echo "No coverage files"; exit 1; fi
+          coverage combine $files
+          coverage xml
+      - uses: codecov/codecov-action@v7
+        continue-on-error: true
+        with:
+          token: ${{ secrets.CODECOV_TOKEN }}
+          files: coverage.xml
+          fail_ci_if_error: false

pico_testing-0.1.0/.github/workflows/codeql.yml

@@ -0,0 +1,21 @@
+name: CodeQL
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  schedule:
+    - cron: "0 6 * * 1"
+
+permissions:
+  security-events: write
+  contents: read
+
+jobs:
+  analyze:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: github/codeql-action/init@v4
+        with: { languages: python }
+      - uses: github/codeql-action/analyze@v4

pico_testing-0.1.0/.github/workflows/docs.yml

@@ -0,0 +1,48 @@
+name: Docs
+on:
+  push:
+    branches: [main]
+    paths: [docs/**, mkdocs.yml]
+  pull_request:
+    branches: [main]
+    paths: [docs/**, mkdocs.yml]
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  validate:
+    if: github.event_name == 'pull_request'
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with: { fetch-depth: 0 }
+      - uses: actions/setup-python@v6
+        with: { python-version: "3.12" }
+      - run: pip install -r docs/requirements.txt
+      - run: mkdocs build --strict
+
+  deploy:
+    if: github.event_name != 'pull_request'
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - uses: actions/checkout@v7
+        with: { fetch-depth: 0 }
+      - uses: actions/setup-python@v6
+        with: { python-version: "3.12" }
+      - run: pip install -r docs/requirements.txt
+      - run: mkdocs build --strict --verbose
+      - uses: actions/upload-pages-artifact@v5
+        with: { path: site }
+      - id: deployment
+        uses: actions/deploy-pages@v5

pico_testing-0.1.0/.github/workflows/publish-to-pypi.yml

@@ -0,0 +1,24 @@
+name: Publish to PyPI
+on:
+  release:
+    types: [published]
+
+permissions:
+  id-token: write
+  contents: read
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+        with: { fetch-depth: 0 }
+      - uses: actions/setup-python@v6
+        with: { python-version: "3.x" }
+      - run: pip install build
+      - run: python -m build
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          skip-existing: true
+          verify-metadata: true
+          attestations: true

pico_testing-0.1.0/.sonarcloud.properties

@@ -0,0 +1,3 @@
+sonar.python.version=3.11, 3.12, 3.13, 3.14
+sonar.sources=src
+sonar.tests=tests

pico_testing-0.1.0/CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-07-10
+
+### Added
+
+- Pytest plugin (entry point `pytest11`) active on install, no conftest wiring.
+- Autouse isolation fixture: sets `PICO_BOOT_AUTO_PLUGINS=false` for every test.
+- `@pytest.mark.pico_auto_plugins` marker to opt back into plugin auto-discovery per test.
+- `make_container(*modules, config=None, boot=False)` fixture with automatic container shutdown on teardown.

pico_testing-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,35 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+
+Examples of unacceptable behavior:
+
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information without explicit permission
+* Other conduct which could reasonably be considered inappropriate
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the project maintainer at **dperezcabrera@gmail.com**.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1.

pico_testing-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing to pico-testing
+
+## Development setup
+
+```bash
+git clone https://github.com/dperezcabrera/pico-testing.git
+cd pico-testing
+python -m venv .venv && source .venv/bin/activate
+pip install -e ".[dev]"
+```
+
+## Running tests
+
+```bash
+pytest tests/ -v
+pytest --cov=pico_testing --cov-report=term-missing tests/
+tox
+```
+
+## Linting
+
+```bash
+ruff check src/ tests/
+ruff format src/ tests/
+```
+
+## Code style
+
+- Python 3.11+
+- See AGENTS.md for conventions
+- Single-line commit messages
+
+## What NOT to do
+
+- Don't modify `_version.py` (auto-generated)
+- Don't change `version_scheme` in pyproject.toml
+- Don't add runtime dependencies without discussion

pico_testing-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 David Pérez Cabrera
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

pico_testing-0.1.0/MANIFEST.in

@@ -0,0 +1,5 @@
+include README.md LICENSE CHANGELOG.md
+recursive-include src *.py py.typed
+recursive-include tests *.py
+exclude .gitignore Dockerfile* docker-compose*.yml Makefile
+prune build dist .tox .pytest_cache __pycache__

pico_testing-0.1.0/PKG-INFO

@@ -0,0 +1,119 @@
+Metadata-Version: 2.4
+Name: pico-testing
+Version: 0.1.0
+Summary: Pytest plugin for the Pico ecosystem: isolated containers by default and a make_container fixture.
+Author-email: David Perez Cabrera <dperezcabrera@gmail.com>
+License: MIT License
+        
+        Copyright (c) 2025 David Pérez Cabrera
+        
+        Permission is hereby granted, free of charge, to any person obtaining a copy
+        of this software and associated documentation files (the "Software"), to deal
+        in the Software without restriction, including without limitation the rights
+        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+        copies of the Software, and to permit persons to whom the Software is
+        furnished to do so, subject to the following conditions:
+        
+        The above copyright notice and this permission notice shall be included in all
+        copies or substantial portions of the Software.
+        
+        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+        SOFTWARE.
+        
+Project-URL: Homepage, https://github.com/dperezcabrera/pico-testing
+Project-URL: Documentation, https://dperezcabrera.github.io/pico-testing/
+Project-URL: Repository, https://github.com/dperezcabrera/pico-testing
+Project-URL: Changelog, https://github.com/dperezcabrera/pico-testing/blob/main/CHANGELOG.md
+Project-URL: Issue Tracker, https://github.com/dperezcabrera/pico-testing/issues
+Keywords: testing,pytest,fixtures,ioc,dependency injection,spring boot
+Classifier: Development Status :: 4 - Beta
+Classifier: Framework :: Pytest
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: OS Independent
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: pico-ioc>=2.2.0
+Requires-Dist: pytest>=8
+Provides-Extra: dev
+Requires-Dist: pytest-asyncio; extra == "dev"
+Requires-Dist: pytest-cov>=5; extra == "dev"
+Requires-Dist: ruff; extra == "dev"
+Requires-Dist: pico-boot>=0.1.0; extra == "dev"
+Dynamic: license-file
+
+# pico-testing
+
+[![PyPI version](https://img.shields.io/pypi/v/pico-testing.svg)](https://pypi.org/project/pico-testing/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![CI](https://github.com/dperezcabrera/pico-testing/actions/workflows/ci.yml/badge.svg)](https://github.com/dperezcabrera/pico-testing/actions/workflows/ci.yml)
+[![codecov](https://codecov.io/gh/dperezcabrera/pico-testing/branch/main/graph/badge.svg)](https://codecov.io/gh/dperezcabrera/pico-testing)
+[![Docs](https://img.shields.io/badge/docs-mkdocs-blue)](https://dperezcabrera.github.io/pico-testing/)
+
+Pytest plugin for the [pico ecosystem](https://github.com/dperezcabrera/pico-ioc): isolated containers by default and a `make_container` fixture with automatic shutdown.
+
+## Why
+
+Any `pico_boot.init()` in a test auto-discovers every pico plugin installed in the venv — so a test suite passes or fails depending on what else happens to be installed. Every pico project ends up copying the same two conftest fixtures. This plugin ships them once:
+
+- **Isolation by default**: `PICO_BOOT_AUTO_PLUGINS=false` is set for every test. Opt back in per-test with `@pytest.mark.pico_auto_plugins`.
+- **`make_container`**: builds containers from explicit modules and config, and shuts them all down on teardown.
+
+## Installation
+
+```bash
+pip install pico-testing
+```
+
+No conftest wiring — installing it activates the plugin.
+
+## Quick start
+
+```python
+import sys
+
+def test_my_service(make_container):
+    container = make_container(
+        "my_package",
+        config={"my_prefix": {"key": "value"}},
+    )
+    service = container.get(MyService)
+    assert service.do_something() == "expected"
+```
+
+`make_container(*modules, config=None, boot=False)`:
+
+- `modules`: module objects or import strings, passed to `init(modules=[...])`.
+- `config`: a plain dict (wrapped in `configuration(DictSource(...))`) or a ready `configuration(...)` object.
+- `boot=True`: use `pico_boot.init` instead of `pico_ioc.init` (plugin auto-discovery still off unless the test is marked).
+
+Re-enable plugin auto-discovery for a single test:
+
+```python
+import pytest
+
+@pytest.mark.pico_auto_plugins
+def test_full_boot(make_container):
+    container = make_container(boot=True)
+```
+
+## Documentation
+
+Full documentation: https://dperezcabrera.github.io/pico-testing/
+
+## License
+
+MIT

pico_testing-0.1.0/README.md

@@ -0,0 +1,62 @@
+# pico-testing
+
+[![PyPI version](https://img.shields.io/pypi/v/pico-testing.svg)](https://pypi.org/project/pico-testing/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![CI](https://github.com/dperezcabrera/pico-testing/actions/workflows/ci.yml/badge.svg)](https://github.com/dperezcabrera/pico-testing/actions/workflows/ci.yml)
+[![codecov](https://codecov.io/gh/dperezcabrera/pico-testing/branch/main/graph/badge.svg)](https://codecov.io/gh/dperezcabrera/pico-testing)
+[![Docs](https://img.shields.io/badge/docs-mkdocs-blue)](https://dperezcabrera.github.io/pico-testing/)
+
+Pytest plugin for the [pico ecosystem](https://github.com/dperezcabrera/pico-ioc): isolated containers by default and a `make_container` fixture with automatic shutdown.
+
+## Why
+
+Any `pico_boot.init()` in a test auto-discovers every pico plugin installed in the venv — so a test suite passes or fails depending on what else happens to be installed. Every pico project ends up copying the same two conftest fixtures. This plugin ships them once:
+
+- **Isolation by default**: `PICO_BOOT_AUTO_PLUGINS=false` is set for every test. Opt back in per-test with `@pytest.mark.pico_auto_plugins`.
+- **`make_container`**: builds containers from explicit modules and config, and shuts them all down on teardown.
+
+## Installation
+
+```bash
+pip install pico-testing
+```
+
+No conftest wiring — installing it activates the plugin.
+
+## Quick start
+
+```python
+import sys
+
+def test_my_service(make_container):
+    container = make_container(
+        "my_package",
+        config={"my_prefix": {"key": "value"}},
+    )
+    service = container.get(MyService)
+    assert service.do_something() == "expected"
+```
+
+`make_container(*modules, config=None, boot=False)`:
+
+- `modules`: module objects or import strings, passed to `init(modules=[...])`.
+- `config`: a plain dict (wrapped in `configuration(DictSource(...))`) or a ready `configuration(...)` object.
+- `boot=True`: use `pico_boot.init` instead of `pico_ioc.init` (plugin auto-discovery still off unless the test is marked).
+
+Re-enable plugin auto-discovery for a single test:
+
+```python
+import pytest
+
+@pytest.mark.pico_auto_plugins
+def test_full_boot(make_container):
+    container = make_container(boot=True)
+```
+
+## Documentation
+
+Full documentation: https://dperezcabrera.github.io/pico-testing/
+
+## License
+
+MIT

pico_testing-0.1.0/SECURITY.md

@@ -0,0 +1,11 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported |
+|---------|-----------|
+| 0.1.x   | Yes       |
+
+## Reporting a Vulnerability
+
+Email dperezcabrera@gmail.com with details. You will receive acknowledgment within 48 hours.

pico_testing-0.1.0/docs/CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-07-10
+
+### Added
+
+- Pytest plugin (entry point `pytest11`) active on install, no conftest wiring.
+- Autouse isolation fixture: sets `PICO_BOOT_AUTO_PLUGINS=false` for every test.
+- `@pytest.mark.pico_auto_plugins` marker to opt back into plugin auto-discovery per test.
+- `make_container(*modules, config=None, boot=False)` fixture with automatic container shutdown on teardown.

pico_testing-0.1.0/docs/faq.md

@@ -0,0 +1,17 @@
+# FAQ
+
+## Why does my suite behave differently after installing pico-testing?
+
+Because that is the point: the plugin sets `PICO_BOOT_AUTO_PLUGINS=false` for every test. If a test relied on auto-discovered plugins, mark it with `@pytest.mark.pico_auto_plugins` — or better, pass its modules explicitly to `make_container`.
+
+## Do I still need my own conftest fixtures?
+
+If your conftest only contained the isolation fixture and a container factory, you can delete both. Project-specific fixtures stay where they are; a local fixture named `make_container` overrides the plugin's.
+
+## Does it work without pico-boot?
+
+Yes. The default path uses `pico_ioc.init`. `pico_boot` is imported only when you call `make_container(boot=True)`.
+
+## Why is shutdown newest-first?
+
+Containers created later may depend on state from earlier ones; tearing down in reverse creation order mirrors how nested resources unwind.

pico_testing-0.1.0/docs/getting-started.md

@@ -0,0 +1,52 @@
+# Getting Started
+
+## Prerequisites
+
+- Python >= 3.11
+- pytest >= 8
+- pico-ioc >= 2.2.0 (pico-boot only if you use `boot=True`)
+
+## Install
+
+```bash
+pip install pico-testing
+```
+
+## Key concepts
+
+| Piece | What it does |
+|---|---|
+| Isolation fixture (autouse) | Sets `PICO_BOOT_AUTO_PLUGINS=false` for every test so `pico_boot.init()` loads only explicit modules |
+| `@pytest.mark.pico_auto_plugins` | Opts a single test back into plugin auto-discovery |
+| `make_container` | Builds containers from explicit modules and config; shuts them all down on teardown |
+
+## make_container
+
+```python
+def test_service(make_container):
+    container = make_container(
+        "my_package",                          # module objects or import strings
+        config={"my_prefix": {"key": "value"}},  # dict or configuration(...) object
+    )
+    service = container.get(MyService)
+```
+
+Signature: `make_container(*modules, config=None, boot=False)`
+
+- `modules` — passed to `init(modules=[...])`. Explicit is the point: list what the test needs.
+- `config` — a plain dict is wrapped in `configuration(DictSource(...))`; a prepared `configuration(...)` passes through.
+- `boot=True` — uses `pico_boot.init` instead of `pico_ioc.init`. Auto-discovery stays off unless the test carries the marker.
+
+Every container created through the fixture is shut down on teardown, newest first.
+
+## Re-enabling auto-discovery
+
+```python
+import pytest
+
+@pytest.mark.pico_auto_plugins
+def test_full_boot(make_container):
+    container = make_container(boot=True)
+```
+
+Use this only for tests that genuinely verify entry-point discovery — everything else should list its modules.

pico_testing-0.1.0/docs/hooks.py

@@ -0,0 +1,7 @@
+import logging
+
+# Suppress griffe warnings about missing type annotations in strict mode.
+# These are cosmetic and don't affect documentation generation.
+# griffe's logger is patched by mkdocstrings to use mkdocs.plugins.* namespace.
+for name in ("griffe", "mkdocs.plugins.griffe", "_griffe"):
+    logging.getLogger(name).setLevel(logging.ERROR)