Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🔥 Avoid setting/imposing TRACE level for everyone #165

Merged
merged 2 commits into from
Jan 30, 2022

Conversation

Ousret
Copy link
Member

@Ousret Ousret commented Jan 30, 2022

Staying as far as humanly possible from any controversial situation.

cf. https://docs.python.org/3/howto/logging.html#custom-levels
A quick search through GH shows that TRACE is often assigned to int:5 but it's not always the case. So to avoid the same situation in another place, I am removing the global assignment.

Staying as far as humanly possible from any controversial situation
@codecov-commenter
Copy link

codecov-commenter commented Jan 30, 2022

Codecov Report

Merging #165 (d222725) into master (db17aa0) will decrease coverage by 0.00%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #165      +/-   ##
==========================================
- Coverage   89.41%   89.40%   -0.01%     
==========================================
  Files          11       11              
  Lines        1200     1199       -1     
==========================================
- Hits         1073     1072       -1     
  Misses        127      127              
Impacted Files Coverage Δ
charset_normalizer/api.py 86.93% <ø> (-0.06%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update db17aa0...d222725. Read the comment docs.

@Ousret Ousret merged commit d2d4217 into master Jan 30, 2022
@Ousret Ousret deleted the avoid-controversial branch January 30, 2022 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants