Uh oh!
There was an error while loading. Please reload this page.
gh-126662: harmonize naming for three namedtuple base classes in urllib.parse - #126663
Merged
Conversation
gpshead
approved these changes
Nov 24, 2024
gpshead
left a comment
Member
There was a problem hiding this comment.
confirmed, this is basically a no-op. nobody ever sees these private base types. may as well have them line up.
ebonnal pushed a commit
to ebonnal/cpython
that referenced
this pull request
Jan 12, 2025
…n urllib.parse (pythonGH-126663) harmonize naming for three namedtuple base classes in urllib.parse
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 freeto 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.
This MR improves naming consistency for three private namedtuples in urllib.parse. This isn't very important, but the consistency helps typeshed. I figured I'd start MRs for gh-126662 with a low-stakes one.