leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Replace print() calls with structured Python logging in analyzer, serp_api, and llm modules #209

New Issue
Closed
opened 2026-03-27 05:23:05 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-27 05:23:05 +00:00
Owner
Copy Link
Copy Source

Context

analyzer.py, serp_api.py, and llm.py use bare print() statements. This makes it impossible to filter by log level, redirect output, or apply consistent formatting in production.

Roadmap reference: ROADMAP.md > P2 > Backend > Add structured logging

What to do

  • Create a shared logger (e.g. logging.getLogger(__name__)) in each module.
  • Replace every print() call with an appropriate logger.debug/info/warning/error() call.
  • Configure the root logger in the application entrypoint to emit JSON or structured text format (include timestamp, level, module).
  • Ensure log level is configurable via LOG_LEVEL environment variable.

Acceptance criteria

  • No print() calls remain in the three listed modules.
  • Running the API with LOG_LEVEL=DEBUG produces structured log output.
  • Running with LOG_LEVEL=WARNING suppresses debug/info messages.
## Context `analyzer.py`, `serp_api.py`, and `llm.py` use bare `print()` statements. This makes it impossible to filter by log level, redirect output, or apply consistent formatting in production. Roadmap reference: ROADMAP.md > P2 > Backend > Add structured logging ## What to do - Create a shared logger (e.g. `logging.getLogger(__name__)`) in each module. - Replace every `print()` call with an appropriate `logger.debug/info/warning/error()` call. - Configure the root logger in the application entrypoint to emit JSON or structured text format (include timestamp, level, module). - Ensure log level is configurable via `LOG_LEVEL` environment variable. ## Acceptance criteria - No `print()` calls remain in the three listed modules. - Running the API with `LOG_LEVEL=DEBUG` produces structured log output. - Running with `LOG_LEVEL=WARNING` suppresses debug/info messages.
AI-Manager added the P2agent-readysmall labels 2026-03-27 05:23:05 +00:00
AI-Manager commented 2026-03-27 06:04:48 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved in the current codebase.

All three modules (analyzer.py, serp_api.py, llm.py) use logging.getLogger(__name__) with a centralized logging.basicConfig() configuration in config.py. No bare print() calls remain in these modules.

Closing as already implemented.

This issue has already been resolved in the current codebase. All three modules (`analyzer.py`, `serp_api.py`, `llm.py`) use `logging.getLogger(__name__)` with a centralized `logging.basicConfig()` configuration in `config.py`. No bare `print()` calls remain in these modules. Closing as already implemented.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#209
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?