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

CLN tidy logger #1439

Merged
merged 3 commits into from
Apr 30, 2023
Merged

CLN tidy logger #1439

merged 3 commits into from
Apr 30, 2023

Conversation

tomMoral
Copy link
Contributor

Duplicate of #1033 that I closed by mistake.

@codecov
Copy link

codecov bot commented Apr 28, 2023

Codecov Report

Patch coverage: 75.00% and project coverage change: -0.03 ⚠️

Comparison is base (41b70ff) 94.78% compared to head (37a6fcb) 94.75%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1439      +/-   ##
==========================================
- Coverage   94.78%   94.75%   -0.03%     
==========================================
  Files          44       44              
  Lines        7207     7308     +101     
==========================================
+ Hits         6831     6925      +94     
- Misses        376      383       +7     
Impacted Files Coverage Δ
joblib/logger.py 87.34% <75.00%> (+0.16%) ⬆️

... and 8 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

amniskin and others added 3 commits April 30, 2023 15:25
using logging.(debug,warning, etc) from within a library is unwise as it forces the end user to have a stream handler on the root logger. Now you'll be logging to the joblib namespace, so that users can specify a logging level via `logging.getLogger('joblib').setLevel(logging.DEBUG)` or whatever they want.
It adds about 10ns to each log use.
@tomMoral tomMoral merged commit 2303143 into joblib:master Apr 30, 2023
14 of 15 checks passed
@tomMoral tomMoral deleted the CLN_tidy_logger branch April 30, 2023 23:13
@jpmaterial
Copy link

Are there perchance any plans already when this will be released?

@tomMoral
Copy link
Contributor Author

tomMoral commented May 2, 2023

Hi, we plan to release joblib in early June.

As we just merged a big refactor, we hope to gather feedbacks before releasing, hence the delay.

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.

None yet

3 participants