-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
GH-123599: url2pathname()
: don't call gethostbyname()
by default
#132610
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
0630a2d
GH-123599: `url2pathname()`: don't call `gethostbyname()` by default
barneygale 26c8688
Docs + tests fixes
barneygale 1bff8b9
This is hard to explain D:
barneygale 4ec391f
Terminology
barneygale 8df17b4
Faffing
barneygale 9e75357
Apply suggestions from code review
barneygale 873c19a
Address some review feedback
barneygale 4bbeef6
Update Lib/urllib/request.py
barneygale 2a42d88
argument -> parameter
barneygale e94ad6a
Merge branch 'main' into gh-123599-resolve-netloc
barneygale File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
8 changes: 3 additions & 5 deletions
8
Misc/NEWS.d/next/Library/2024-11-14-21-17-48.gh-issue-126838.Yr5vKF.rst
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,3 @@ | ||
Fix issue where :func:`urllib.request.url2pathname` mishandled file URLs with | ||
authorities. If an authority is present and resolves to ``localhost``, it is | ||
now discarded. If an authority is present but *doesn't* resolve to | ||
``localhost``, then on Windows a UNC path is returned (as before), and on | ||
other platforms a :exc:`urllib.error.URLError` is now raised. | ||
Add *resolve_host* keyword-only parameter to | ||
:func:`urllib.request.url2pathname`, and fix handling of file URLs with | ||
authorities. |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder, should we check this before calling
gethostname()
which can fail?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm struggling to come up with firm info on when
gethostname()
fails (or whether it can perform network access). Do you have any pointers? Thanks.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not know.
But I was thinking about this case: processing the "file:" URL on different computer. We cannot use
gethostname()
, because it returns a different result. If we want to get a path on other computer, we should ignore the host name. There will still be problem with processing Windows paths on Posix and Posix paths on Windows.I do not know how common this case, and how common the opposite case, when we only use
gethostname()
, but notgethostbyname()
. We should guess what would be more useful for users without having any data.