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

Refactor: replace print() calls with structured logging in analyzer.py, serp_api.py, and llm.py #882

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

Context

Multiple backend modules use print() for output instead of Python's logging module. This makes it impossible to control log levels, route logs to files, or integrate with log aggregators.

Roadmap reference: P2 Backend - Add structured logging

What to do

  1. Replace all print() calls in analyzer.py, serp_api.py, and llm.py with calls to a named logger (e.g. logging.getLogger(__name__)).
  2. Configure a root logger in api.py startup that sets level and format based on a LOG_LEVEL environment variable (default: INFO).
  3. Use appropriate log levels: DEBUG for verbose tracing, INFO for normal events, WARNING/ERROR for problems.
  4. Scan all other backend files for stray print() calls and fix those too.

Acceptance criteria

  • No print() calls remain in backend source files (excluding tests).
  • LOG_LEVEL=DEBUG produces verbose output; LOG_LEVEL=WARNING suppresses info logs.
  • Log lines include timestamp, level, module name, and message.
## Context Multiple backend modules use `print()` for output instead of Python's `logging` module. This makes it impossible to control log levels, route logs to files, or integrate with log aggregators. Roadmap reference: P2 Backend - Add structured logging ## What to do 1. Replace all `print()` calls in `analyzer.py`, `serp_api.py`, and `llm.py` with calls to a named logger (e.g. `logging.getLogger(__name__)`). 2. Configure a root logger in `api.py` startup that sets level and format based on a `LOG_LEVEL` environment variable (default: `INFO`). 3. Use appropriate log levels: DEBUG for verbose tracing, INFO for normal events, WARNING/ERROR for problems. 4. Scan all other backend files for stray `print()` calls and fix those too. ## Acceptance criteria - No `print()` calls remain in backend source files (excluding tests). - `LOG_LEVEL=DEBUG` produces verbose output; `LOG_LEVEL=WARNING` suppresses info logs. - Log lines include timestamp, level, module name, and message.
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-29 05:22:48 +00:00
AI-Manager commented 2026-03-29 06:03:37 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved. The changes are already merged into main.

All print() calls replaced with structured logging (logging.getLogger). No print() calls remain in backend source files.

Closing as completed.

This issue has been resolved. The changes are already merged into main. All print() calls replaced with structured logging (logging.getLogger). No print() calls remain in backend source files. Closing as completed.
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 refactor 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#882
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?