On 23 November 2017 at 12:49, Antoine Pitrou <solip...@pitrou.net> wrote:
> On Thu, 23 Nov 2017 12:39:46 +0100 > Ivan Levkivskyi <levkivs...@gmail.com> wrote: > > > > Also I think it makes sense to keep discussion in one place, i.e. either > > here xor at https://bugs.python.org/issue10544 > > The bug tracker can be used for implementation discussions, but general > language design decisions (such as whether to allow or not a certain > construct) should take place on python-dev. > > I'm still in favour of deprecating and then disallowing. Nobody seems > to have presented a real-world use case that is made significantly > easier by trying to "fix" the current behaviour (as opposed to > spelling the loop explicitly). I do asynchronous programming using > "yield" every day in may job (because of compatibility requirements > with Python 2) and I've never had once the need to write a "yield" > inside a comprehension or generator expression. > > "I don't use it, therefore it is not needed" is a great argument, thanks. Lets just forget about two SO questions and dozens people who up-voted it. Do you use async comprehensions? If not, then we don't need them either. -- Ivan
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
