-
-
Notifications
You must be signed in to change notification settings - Fork 596
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
B404 Consider possible security implications associated with DEVNULL module. #666
Comments
On a related note, it seems to miss the fact that I'm using |
Please open a separate issue for the |
Actually #619 already captures the asyncio bit. |
Forgot I already opened that. :P This error should therefore probably not appear at all, as I've only imported a couple of flags, there shouldn't be any security considerations for that. |
This change modifies the warning using subprocess module. The module is subprocess, and anything else is a submodule or function. Fixes #666 Signed-off-by: Eric Brown <browne@vmware.com>
This change modifies the warning using subprocess module. The module is subprocess, and anything else is a submodule or function. Fixes PyCQA#666 Signed-off-by: Eric Brown <browne@vmware.com>
This change modifies the warning using subprocess module. The module is subprocess, and anything else is a submodule or function. Fixes PyCQA#666 Signed-off-by: Eric Brown <browne@vmware.com>
from subprocess import DEVNULL, PIPE
produces
B404 Consider possible security implications associated with DEVNULL module.
That's awfully confusing. I think it's meant to say 'subprocess module'.
The text was updated successfully, but these errors were encountered: