Add support for PyYAML v6 #96
Merged
Conversation
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
adamgreig
approved these changes
Jan 18, 2022
Member
adamgreig
left a comment
adamgreig
left a comment
There was a problem hiding this comment.
Thanks!
Do you know of anything that needs a release with this now or can it wait til the next release?
bors merge
Member
Author
I think it can wait until the next release 👍 |
Contributor
|
Build succeeded: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changelog: https://github.com/yaml/pyyaml/releases/tag/6.0
PyYAML released version 6, and the only breaking change is "always require
Loaderarg toyaml.load()", which would have resulted in a deprecation warning with version 5.Supporting both 5 and 6 makes this easier for people to use during the transition phase because PyYAML is often provided as an OS package on Linux distributions.