Skip to content

fix: resolve should_print from NOTSET to False default#149

Draft
hussein-awala wants to merge 1 commit intomainfrom
fix/should-print-notset-default
Draft

fix: resolve should_print from NOTSET to False default#149
hussein-awala wants to merge 1 commit intomainfrom
fix/should-print-notset-default

Conversation

@hussein-awala
Copy link
Owner

Summary

  • should_print in submit_app was never resolved from its NOTSET sentinel value to an actual boolean
  • ArgNotSet() is truthy, so LoggingMixin.log() would call print() instead of using the logger when callers didn't explicitly pass should_print=False

Test plan

  • Verify submit_app() without should_print uses the logger (not stdout)
  • Verify submit_app(should_print=True) still prints to stdout

🤖 Generated with Claude Code

The should_print parameter was never resolved from NOTSET. Since
ArgNotSet() is truthy, this caused unintended printing to stdout
instead of logging when callers didn't explicitly pass should_print.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant