bpo-34132: Fix netrc parsing regression#8320
Closed
bbayles wants to merge 2 commits into
Closed
Conversation
Contributor
Author
|
I found another regression; I'll close and re-submit. |
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
3 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.
This PR adds a test and fix for the issue described in bpo-34132, a strange regression in netrc parsing that causes recent versions of Python 3 to fail to parse files like this:
but to succesfully parse files like this:
This fix is adapted from the Python 2 version, which is able to parse the former file.
https://bugs.python.org/issue34132