Code quality: resolve unsafe URL access (ruff Bandid S310)#378
Open
Code quality: resolve unsafe URL access (ruff Bandid S310)#378
Conversation
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
mgovers
added
the
improvement
mgovers
changed the title
Signed-off-by: Martijn Govers <martijn.govers@alliander.com>
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR resolves the bandid issue reported in #377
It also shifts to
safe_*which use keyword arguments and deprecates the existing*which does not. This enables future compatibility and also pushes people to think about actually using only safe utilities.