-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
gh-133551: Support t-strings in annotationlib #133553
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
Conversation
I don't know why you'd use t-strings in annotations, but now if you do, the STRING format will do a great job of recovering the source code.
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.
Apart from @AA-Turner's comments, content looks good!
Co-authored-by: Adam Turner <[email protected]>
Thanks @JelleZijlstra for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
I don't know why you'd use t-strings in annotations, but now if you do, the STRING format will do a great job of recovering the source code. (cherry picked from commit 90f476e) Co-authored-by: Jelle Zijlstra <[email protected]>
GH-133628 is a backport of this pull request to the 3.14 branch. |
|
|
|
|
|
|
|
…3628) gh-133551: Support t-strings in annotationlib (GH-133553) I don't know why you'd use t-strings in annotations, but now if you do, the STRING format will do a great job of recovering the source code. (cherry picked from commit 90f476e) Co-authored-by: Jelle Zijlstra <[email protected]>
|
|
|
|
|
|
|
|
|
|
I don't know why you'd use t-strings in annotations, but now if you do, the STRING format will do a great job of recovering the source code.
I don't know why you'd use t-strings in annotations, but now if you do,
the STRING format will do a great job of recovering the source code.