(cherry-pick) Fix: address issues pointed out by Python scanners (#3036) #3045
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.
Description
Our Python scanners point out issues regarding the use of the subprocess module. The issues tend to be in 2 main categories:
The use of subprocess.Popen() directly is discouraged. Instead, the scanners recommend using run, call, or checked_call.
The use of any of the subprocess calls with shell=True is forbidden, because it is prone to code injection attacks. Instead, the scanners require shell=False or omitting shell altogether.
Collateral (docs, reports, design examples, case IDs): Python scans when preparing the release.
Tests added:
Tests run:
CI and manual testing of rtl_src_config.