Update FAQ entry for default_flow_style to reflect PyYAML 5.1 changes #19
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
This behavior led to some confusion recently as we have some boxes running PyYAML 5.3 and some running older PyYAML. Code originally written for 5.3 produced different output on older releases. This change adds clarification to the FAQ entry for default_flow_style which mentions that the default behavior changed in version 5.1.
terminalmage
force-pushed
the
default_flow_style
branch
from
2c1dc30 to
ed9c4c3
Compare
awmackowiak
approved these changes
Jun 25, 2024
|
Is there something else needed to get this merged and get the docs updated? |
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.
This behavior led to some confusion recently as we have some boxes running PyYAML 5.3 and some running older PyYAML. Code originally written for 5.3 produced different output on older releases.
This change adds clarification to the FAQ entry for default_flow_style which mentions that the default behavior changed in version 5.1.