fix(warnings): trigger reset
warnings at a better stack level
#165
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.
#164 upgraded ruff to include more flake8 bugbear errors, which highlighted that the
stacklevel
argument towarnings.warn
is not used by the warning checker. This results in warnings being attached to an unhelpful decoy-internal call-site.This PR uses the
stacklevel
argument ofwarnings.warn
to trigger the warnings at whatever level calleddecoy.reset
. For pytest usage, this results in something like the following: