Repository navigation
gh-161317: configparser.write() raises InvalidWriteError for multiline values with leading whitespace - #161337
Closed
BHUVANSH855 wants to merge 1 commit into
Closed
BHUVANSH855 wants to merge 1 commit into
BHUVANSH855 wants to merge 1 commit into
Conversation
…ltiline values with leading whitespace
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
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.
Issue: gh-161317
configparser.write()would silently produce output that read back differently when a value contained a continuation line with leading whitespace — the whitespace was stripped on read-back with no error.Fix: Raise
InvalidWriteErrorwhen a value's continuation line starts with a space or tab, consistent with the existing guard for keys with leading whitespace (gh-96239).