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

Showing content from https://mail.python.org/pipermail/python-dev/2012-April/118623.html below:

[Python-Dev] Change to yield-from implementation

• Previous message: [Python-Dev] Removing surplus fields from the frame object and not adding any new ones.
• Next message: [Python-Dev] Change to yield-from implementation
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Mark Shannon wrote:

> We have recently removed the f_yieldfrom field from the frame object.
> (http://bugs.python.org/issue14230)

Hey, wait a minute. Did anyone consider the performance effect
of that change on deeply nested yield-froms?

The way it was, a yield-from chain was traversed by a very
tight C loop that found the end frame and resumed it directly.
If I understand what you've done correctly, now it has to
enter and execute a bytecode in every frame along the way.

-- 
Greg

• Previous message: [Python-Dev] Removing surplus fields from the frame object and not adding any new ones.
• Next message: [Python-Dev] Change to yield-from implementation
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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