[issue24327] yield unpacking

2015-05-30 Thread Ethan Furman
Ethan Furman added the comment: I was waiting a couple days to give Mital a chance to clarify if some other behavior was intended. -- ___ Python tracker ___

[issue24327] yield unpacking

2015-05-30 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Pyt

[issue24327] yield unpacking

2015-05-30 Thread Josh Rosenberg
Josh Rosenberg added the comment: Should someone be closing this with "yield from already exists"? -- nosy: +josh.r ___ Python tracker ___ ___

[issue24327] yield unpacking

2015-05-29 Thread Ethan Furman
Ethan Furman added the comment: Do you mean something like: --> def heh(): ... yield [1, 2, 3] ... --> for i in heh(): ... print(i) ... [1, 2, 3] # *grumble* --> def heh(): ... for i in [1, 2, 3]: ... yield i ... --> for i in heh(): ... print(i) ... 1 2 3 If so, use `yield from

[issue24327] yield unpacking

2015-05-29 Thread Mital Ashok
New submission from Mital Ashok: (This is more of a feature request than a bug, but https://www.python.org/dev/peps/pep-0042/ said to post it here) My request is to have syntax like this: yield *iterable to lazily return the iterable's items, not much unlike: # ... for i in itera