The byte code for the embedded expressions is all produced during the regular byte code generation phase. On Tue, Sep 8, 2015 at 3:30 AM, Erik <python at lucidity.plus.com> wrote: > 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. > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > https://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > https://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (python.org/~guido) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20150908/fbc331be/attachment.html>
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