Ignore bogus pylint "security" issue #6473
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<pylint-dev/pylint#5322> describes a crash when using a specific extension that we don't use, and really isn't a security issue at all. Ideally we'd upgrade pylint anyways, but we've fallen a bit behind and it isn't a trivial version bump.
zenmonkeykstop
approved these changes
Jun 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Status
Ready for review
Description of Changes
pylint-dev/pylint#5322 describes a crash when
using a specific extension that we don't use, and really isn't a
security issue at all.
Ideally we'd upgrade pylint anyways, but we've fallen a bit behind
and it isn't a trivial version bump.
Testing
make safety, observe it complains about nothingDeployment
Any special considerations for deployment? No
Checklist