A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-September/141508.html below:

[Python-Dev] PEP 498: Literal String Interpolation is ready for pronouncement

[Python-Dev] PEP 498: Literal String Interpolation is ready for pronouncement [Python-Dev] PEP 498: Literal String Interpolation is ready for pronouncementErik python at lucidity.plus.com
Tue Sep 8 12:30:55 CEST 2015
Hi.

I realise I'm coming late to the party on this, but I have a question 
about something I don't think the PEP makes clear.



When is the bytecode for the embedded expressions created?



Is it when the source code is parsed, or at runtime when the f-string is 
evaluated?

If the latter, then any process that works on bytecode (introspection 
tools, peep-hole optimisers etc) will need work.

I understand that colorising editors and analysis tools which operate at 
the source code level will need work, that's fair enough.


The PEP hints at things in this area in the "Specification", "Code 
equivalence" and "Expression evaluation" sections, and my guess is that 
it will (and should) happen during parsing, but I can't see where it 
comes right out and says it.

Thanks, E.
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4