Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
bpo-27122: Fix comment to point to correct issue ##47
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
It took me quite a bit to figure out what this was referring to, since the given issue number is wrong, and the original commit message I found through git blame lists a different, also wrong issue number... seehttps://bugs.python.org/issue27122#msg279449
Codecov Report
@@ Coverage Diff @@## master #47 +/- ##==========================================- Coverage 82.37% 82.37% -0.01%========================================== Files 1427 1427 Lines 350948 350948 ==========================================- Hits 289089 289083 -6- Misses 61859 61865 +6 Continue to review full report at Codecov.
|
berkerpeksag approved these changesFeb 12, 2017
berkerpeksag pushed a commit that referenced this pull requestFeb 12, 2017
It took me quite a bit to figure out what this was referring to,since the given issue number is wrong, and the original commitmessage I found through git blame lists a different, also wrongissue number... seehttps://bugs.python.org/issue27122#msg279449(cherry picked from commitaf88e7e)
berkerpeksag pushed a commit that referenced this pull requestFeb 12, 2017
It took me quite a bit to figure out what this was referring to,since the given issue number is wrong, and the original commitmessage I found through git blame lists a different, also wrongissue number... seehttps://bugs.python.org/issue27122#msg279449(cherry picked from commitaf88e7e)
iritkatriel referenced this pull request in iritkatriel/cpythonJul 23, 2021
jaraco pushed a commit that referenced this pull requestDec 2, 2022
isidentical referenced this pull request in isidentical/cpythonMar 22, 2023
oraluben pushed a commit to oraluben/cpython that referenced this pull requestJun 27, 2023
This was referencedFeb 11, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
None yet
4 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.
It took me quite a bit to figure out what this was referring to, since the given issue number is wrong, and the original commit message I found through git blame lists a different, also wrong issue number... seehttps://bugs.python.org/issue27122#msg279449
Here's the correct issue link to confirm:https://bugs.python.org/issue27122