-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[flake8-bandit
] Move unsafe-markup-use
from RUF035
to S704
#15957
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[flake8-bandit
] Move unsafe-markup-use
from RUF035
to S704
#15957
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Thanks, this has to wait for the next minor release because it's breaking (selecting |
|
code | total | + violation | - violation | + fix | - fix |
---|---|---|---|---|---|
S704 | 30 | 30 | 0 | 0 | 0 |
RUF035 | 9 | 0 | 9 | 0 | 0 |
Clever, no :) But what I'd do is to lift the |
Switches to more verbose labels for references section.
44eec2b
to
e4e1c58
Compare
Thanks @Daverball for rebasing |
…15957) ## Summary `RUF035` has been backported into bandit as `S704` in this [PR](PyCQA/bandit#1225) This moves the rule and its corresponding setting to the `flake8-bandit` category ## Test Plan `cargo nextest run` --------- Co-authored-by: Micha Reiser <micha@reiser.io>
…15957) ## Summary `RUF035` has been backported into bandit as `S704` in this [PR](PyCQA/bandit#1225) This moves the rule and its corresponding setting to the `flake8-bandit` category ## Test Plan `cargo nextest run` --------- Co-authored-by: Micha Reiser <micha@reiser.io>
Summary
RUF035
has been backported into bandit asS704
in this PRThis moves the rule and its corresponding setting to the
flake8-bandit
categoryTest Plan
cargo nextest run