Skip to content
This repository has been archived by the owner on Jul 5, 2023. It is now read-only.

Only evaluate expensive logging statements when in logging level #58

Open
hacker-h opened this issue Aug 23, 2019 · 0 comments
Open

Only evaluate expensive logging statements when in logging level #58

hacker-h opened this issue Aug 23, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@hacker-h
Copy link
Contributor

We should use https://docs.python.org/3/howto/logging.html#optimization for "expensive" methods like test_orchestrator/collect_results.py and only evaluate them if we are in the actual logging level.

@hacker-h hacker-h added the enhancement New feature or request label Aug 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant