-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
Remove blacklist call to input() #662
Conversation
Now that bandit 1.6.3 is Python 3.x only, there is no longer a need to check for a Python 2.x security issue. Namely, input() is considered safe in Python 3.x. Fixes #596 Signed-off-by: Eric Brown <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Not a big issue, but just to note: this change is backwards incompatible, we were running |
…r it, therefore it no longer exists. See Bandit issue PyCQA/bandit#662 .
Now that bandit 1.6.3 is Python 3.x only, there is no longer a need to check for a Python 2.x security issue. Namely, input() is considered safe in Python 3.x. Fixes PyCQA#596 Signed-off-by: Eric Brown <[email protected]>
Now that bandit 1.6.3 is Python 3.x only, there is no longer a need to check for a Python 2.x security issue. Namely, input() is considered safe in Python 3.x. Fixes PyCQA#596 Signed-off-by: Eric Brown <[email protected]>
Now that bandit 1.6.3 is Python 3.x only, there is no longer a
need to check for a Python 2.x security issue. Namely, input()
is considered safe in Python 3.x.
Fixes #596
Signed-off-by: Eric Brown [email protected]