➜

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 yselivanov
Recipients Inyeol.Lee, Jim Fasarakis-Hilliard, arigo, belopolsky, benjamin.peterson, danielsh, emptysquare, erickt, esc24, georg.brandl, glyph, gvanrossum, levkivskyi, ncoghlan, rhettinger, serhiy.storchaka, yselivanov
Date 2017-11-23.16:42:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511455356.53.0.213398074469.issue10544@psf.upfronthosting.co.za>
In-reply-to
Content 
> Well, after all I am thinking maybe it is indeed makes sense to ban `yield` inside both sync/async and both comprehensions/generator expressions.

I agree, as I can't imagine a real use case for

   a = ((yield a) for a in as)

which is really equivalent to

   def a():
      for a in as:
         yield (yield a)
History
Date User Action Args
2017-11-23 16:42:36yselivanovsetrecipients: + yselivanov, gvanrossum, arigo, georg.brandl, rhettinger, ncoghlan, belopolsky, benjamin.peterson, erickt, glyph, Inyeol.Lee, serhiy.storchaka, esc24, danielsh, emptysquare, levkivskyi, Jim Fasarakis-Hilliard
2017-11-23 16:42:36yselivanovsetmessageid: <1511455356.53.0.213398074469.issue10544@psf.upfronthosting.co.za>
2017-11-23 16:42:36yselivanovlinkissue10544 messages
2017-11-23 16:42:36yselivanovcreate