This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author qwjqwj
Recipients pitrou, qwjqwj
Date 2009-03-27.16:52:20
SpamBayes Score 1.8477262e-07
Marked as misclassified No
Message-id <1238172742.56.0.406156464826.issue5577@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, I see. Thanks.
However, I don't think yield should be consumed at the iterator's level.
It may be more useful for the outside function to consume the yield.

For example, some function want to change some data with another "thread".

def f():
    ...fetch data...
    x = [yield i for i in data]

It should be written as belowed in Python 3.1 now
def f():
    x = []
    for i in data:
        x.append((yield i))
History
Date User Action Args
2009-03-27 16:52:22qwjqwjsetrecipients: + qwjqwj, pitrou
2009-03-27 16:52:22qwjqwjsetmessageid: <1238172742.56.0.406156464826.issue5577@psf.upfronthosting.co.za>
2009-03-27 16:52:21qwjqwjlinkissue5577 messages
2009-03-27 16:52:20qwjqwjcreate