On Thu, 23 Nov 2017 12:39:46 +0100 Ivan Levkivskyi <levkivskyi at 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. Regards Antoine.
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