| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
Let's add a test that checks that instantiating an Interpolation without an expression actually populates expression with the empty string and it's good to go!
Sorry, something went wrong.
Sure; done! |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM! Thanks @davepeck!
Sorry, something went wrong.
|
Thanks @davepeck for the PR, and @lysnikolaou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
…ssion` (pythonGH-136441) (cherry picked from commit f1b8d01) Co-authored-by: Dave Peck <davepeck@gmail.com>
|
GH-136511 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
…n.expression` (pythonGH-136441) (python#136511) Co-authored-by: Dave Peck <davepeck@gmail.com>
| Back | FazBrowse Home | New Git URL |
Per pending updates to PEP 750, we now provide an empty string default for Interpolation.expression.
If you're using t-string literals, Interpolation.expression is set to the original source text. But if you're writing code that creates Interpolation instances directly, there isn't always an obvious choice for expression.