Replace print() with logging module throughout server scripts #5

New issue

Open

opened 2026-04-06 22:25:19 -07:00 by pyr0ball · 0 comments

pyr0ball commented

2026-04-06 22:25:19 -07:00

Owner

Summary

Both server scripts use bare print() throughout (~25 calls in voice_server.py, ~20 in voice_server_enhanced.py). CF convention is the logging module. The .env.example already defines LOG_LEVEL and LOG_FILE but the server code never reads them.

Action

Replace all print() with logging.info/warning/error/debug
Read LOG_LEVEL and LOG_FILE from config at startup
Use logging.basicConfig or a structured logger

References

cf-dev review finding: Priority 4
Python rules: print() in edited files should use logging module

## Summary Both server scripts use bare `print()` throughout (~25 calls in `voice_server.py`, ~20 in `voice_server_enhanced.py`). CF convention is the `logging` module. The `.env.example` already defines `LOG_LEVEL` and `LOG_FILE` but the server code never reads them. ## Action - Replace all `print()` with `logging.info/warning/error/debug` - Read `LOG_LEVEL` and `LOG_FILE` from config at startup - Use `logging.basicConfig` or a structured logger ## References - cf-dev review finding: Priority 4 - Python rules: print() in edited files should use logging module