🧑💻 Maintenance: Log current vidgear version when vidgear APIs are called, not at import. (Fixes #338) #348
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief Description
This PR will add functionality to log current vidgear version once only when vidgear APIs are called, not at import. Less clutter in logs.
Requirements / Checklist
Related Issue
#338
#340
Context
This PR is aimed at reducing unnecessary logging of vidgear current version on importing its APIs. With this PR, user can now completely turn off logging and moreover APIs with logging turned on (
logging=True
) will automatically log version only once when called within code, thus serving both purposes.Types of changes