Specify yaml.FullLoader in yaml.load_all statement #75
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
Signed off by: Matthew Field <[email protected]>
|
Is this project still maintained? |
|
Abandoning this PR. Project doesn't seem active. |
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.
Currently, running kube-shell shows a PyYAML Loader deprecation warning because the yaml Loader type isn't specified in two "yaml.load_all" calls.
As per PyYAML documentation, after showing the warning, PyYAML defaults to using the FullLoader.
This change explicitly sets the FullLoader, which will suppress the error in a non-future-breaking way - that is, if a future PyYAML version exits instead of warning & defaulting when a Loader type is not specified.
Fixes #71
Fixes #73
Signed off by: Matthew Field [email protected]