fix: Add get_log_level API to query current logging level (fixes #1345) #1346
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.
Summary
Expose a small getter for the logger: get_log_level(). This complements set_log_level() and lets callers/tests query and restore verbosity safely. Re-exported from the top-level fortplot module.
Changes
Verification
Commands
Key output excerpts
Artifacts
Notes
Reviewer self-check (automation)
make test-ci— passed (fast CI set).fpm test --target test_log_level_getter,fpm test --target test_log_level_input_validation— compiled successfully.LOG_LEVEL_DEBUGindoc/mpeg_validation.md.Evidence
No further changes required for production readiness.
\nDocs\n- Added usage example for get_log_level() and safe restore pattern in doc/warning_system.md.\n
Follow-up fixes