print() left in Python source
Part of Code Quality & Syntax, which counts for 20% of the overall score. When this check fires it deducts 2 points from that category, once per scan, no matter how many places it turns up.
What it detects
print() debugging statements left outside of scripts/CLI entrypoints; prefer a logger.
Why it matters
print() writes to stdout with no level, no timestamp, and no way to filter or route the output to a log aggregator. Behind a WSGI/ASGI server in production the output may be buffered, interleaved, or dropped, so the one time you need those messages they are gone.
How to fix it
Replace print() calls in application and library code with the logging module: create a module-level logger via logging.getLogger(__name__) and call logger.debug or logger.info, configuring logging once at the entrypoint. Prints in CLI scripts and __main__ entrypoints are fine and this check already skips them. Enable Ruff rule T201 (flake8-print) to keep new ones out.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo