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-May/139875.html below:

[Python-Dev] PEP 492 quibble and request

[Python-Dev] PEP 492 quibble and request [Python-Dev] PEP 492 quibble and requestArnaud Delobelle arnodel at gmail.com
Sun May 3 21:03:09 CEST 2015
On 3 May 2015 at 02:22, Greg Ewing <greg.ewing at canterbury.ac.nz> wrote:
> Guido van Rossum wrote:
>>
>> On Sat, May 2, 2015 at 1:18 PM, Arnaud Delobelle <arnodel at gmail.com
>> <mailto:arnodel at gmail.com>> wrote:
>>
>>     Does this mean that
>>     somehow "await x" guarantees that the coroutine will suspend at least
>>     once?
>
>
> No. First, it's possible for x to finish without yielding.
> But even if x yields, there is no guarantee that the
> scheduler will run something else -- it might just
> resume the same task, even if there is another one that
> could run. It's up to the scheduler whether it
> implements any kind of "fair" scheduling policy.

That's what I understood but the example ('yielding()') provided by
Ron Adam seemed to imply otherwise, so I wanted to clarify.

-- 
Arnaud
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