python-logging
Python Logging
Overview
Choose the logging system based on project needs. Core principle: stdlib logging for libraries and ecosystem integration, loguru for fast, simple app/CLI logging.
Quick Reference
| Need | Use |
|---|---|
| Library or long-lived service | stdlib logging |
| Simple app or CLI | loguru |
| Integrations (Sentry/OTel) | stdlib logging |
Decision Rules
Use stdlib logging when:
- Building a reusable library
- You need handler hierarchies or integration with ops tooling
More from narumiruna/telegram-bot
aiogram-framework
Build, refactor, or troubleshoot Telegram bots using aiogram v3. Use when working with aiogram routers/handlers/filters, Dispatcher lifecycle, update delivery (long polling or webhook), FSM, middleware/DI, error handling, or aiogram utilities like keyboards, formatting, and i18n.
181python-modern-tooling
Use when choosing the right modern Python tooling workflow for a project or script (uv setup, quality tools, CLI, logging, packaging) or when unsure which Python tooling skill applies.
15python-packaging-uv
Use when building or publishing Python packages with uv, including dist artifacts and pre-publish checks.
15python-cli-typer
Use when building or structuring Python CLI commands with Typer, including commands, options, and multi-command apps.
14uv-scripts
Use when running or authoring standalone Python scripts with uv, especially when choosing Python versions, adding one-off dependencies, using no-project mode, or embedding inline script metadata.
14python-uv-project-setup
Use when initializing a Python project or script, adding dependencies, or running commands with uv, especially to avoid pip install and direct python/pytest usage.
12