gh-68443: Replace debug level-related logic in http client with logging#8633
gh-68443: Replace debug level-related logic in http client with logging#8633CuriousLearner wants to merge 2 commits into
Conversation
|
Hey @bitdancer , @vsajip Can you please have a look at this? I just noticed this PR wasn't reviewed from almost a year. Please let me know, what is needed here. Thanks! |
Sorry, something went wrong.
|
@CuriousLearner I would go ahead and rebase to resolve conflicts. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
9933ad5 to
b6997e1
Compare
November 14, 2025 00:49
Replace debuglevel-based print statements with Python's standard logging module for better integration with logging frameworks and log aggregation tools like Sentry. Uses % formatting consistently for better log pattern matching in aggregation tools.
c240289 to
afeb73c
Compare
December 7, 2025 02:13
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
tpikonen
left a comment
There was a problem hiding this comment.
I ran into the problem (logging with print, which gives no timestamps etc.) this PR is fixing, and I hope it gets merged.
But, this patch has several style-related changes, which should be put into a separate commit. It also looks to me that there is some print usage left and some debug output which this patch removes, see my comments.
Sorry, something went wrong.
Hey @bitdancer , here's the PR for issue: https://bugs.python.org/issue24255
https://bugs.python.org/issue24255