Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32.1k
[backport to 3.6] bpo-27122: Fix comment to point to correct issue number (#47)#48
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
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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)
Codecov Report
@@ Coverage Diff @@## 3.6 #48 +/- ##====================================== Coverage ? 82.37% ====================================== Files ? 1427 Lines ? 350948 Branches ? 0 ====================================== Hits ? 289099 Misses ? 61849 Partials ? 0
Continue to review full report at Codecov.
|
Emit FSTRING_MIDDLE for literal after last expression and before quotes
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(cherry picked from commitaf88e7e)