bpo-32917: make ConfigParser blank line writing controllable#5846
Conversation
Add two arguments *trim_final_blankline* and *blankline_around_sections* to control the behavior of :meth:`ConfigParser.write` in writing blank lines.
This pull request was closed.
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
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.
New arguments trim_final_blankline and blankline_around_sections for
configparser.ConfigParser.writeIf blankline_around_sections is true (the default), a blank line will be inserted after each section.
If trim_final_blankline is true, the final blank line after the last section will not be inserted.
https://bugs.python.org/issue32917
https://bugs.python.org/issue32917