Fix incorrect use of raise with warnings.warn
in scenario switcher
#1196
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.
Part of #1181.
Fixes an incorrect use of
raise
statement with a call towarnings.warn
(raise
should be used with anException
subtype while the recommended approach for outputting warnings is to callwarnings.warn
). Also removes the global Pylint E0702 rule ignore frompyproject.toml
that flags this previous usage as a violation.