Fix: reduce number of deprecation warnings #1135
Merged
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.
The
@lektor.utils.deprecated
decorator introduced in #1113 uses thewarnings.catch_warnings
context manager to suppress deprecation warnings generated within the body of deprecated functions.As it turns out, there is (arguably) a bug in Python's warnings module, such that every use of
warnings.catch_warnings
essentially erases all record of which warnings have been displayed.This breaks the "default" setting of the warnings filter which is supposed to ensure that each warning is only displayed once per (module, line).
So here, we disuse catch_warnings.
Description of Changes