[euscollada/parseColladaBase.py] always explicitly indicating SafeLoader when using yaml.load #2
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
…type (SafeLoader?) when using yaml.load function to avoid error caused by PyYAML version
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.
Same to the last PR:
yaml.load function requires Loader argument to be explicitly indicated after PyYAML version '5.4.1'
yaml/pyyaml#576
yaml/pyyaml#561 -- always require Loader arg to yaml.load()
Always explicitly indicating Loader type to SafeLoader with no need of comparing PyYAML version may be a better solution?
(Though the default Loader is FullLoader before and including version '5.4.1')