How to integrate hypercorn's loggers into existing logging setup

[dkbarn]

I am using hypercorn in my application with the Python API rather than the command line. How can I integrate hypercorn's logging into an existing python logging hierarchy? From looking at the source of logging.py, there is no way for hypercorn to create only the Logger objects without the Handler objects.

It is not the responsibility of a library to create and manage logging Handlers -- this is the job of the top-level application to control, which all dependent library's will adopt. So it makes sense for hypercorn to create the Handlers when using the command line since it is the top-level application. But when importing it into a Python application, it should only create the Loggers and not the Handlers, so that all log messages from the entire application share the same setup.

How can this be achieved?

[nabheet]

This is how I did it:

logger = logging.getLogger(__name__)
...
    config = Config()
    config.accesslog = logger
    config.errorlog = logger
...
    run(config)

[jbbqqf]

Hi! Triaging older issues — this reads more like a usage / config question than a bug, and an answer is already in the thread.

Programmatic logger integration is a documented usage pattern.

Evidence:

• comment — nabheet: pass config.accesslog = logger; config.errorlog = logger.
• src/hypercorn/logging.py:32-34 — _create_logger returns the target unchanged when it is already a Logger instance — supported integration path.

If you'd like to keep this open as a documentation request, please ignore — otherwise would you mind closing this out?

---

Disclosure: I drafted this comment with help from Claude Code while triaging stale issues; the references above were verified manually.