On 2015-05-01 4:24 PM, Arnaud Delobelle wrote: > On 1 May 2015 at 20:24, Yury Selivanov <yselivanov.ml at gmail.com> wrote: >> On 2015-05-01 3:19 PM, Ethan Furman wrote: > [...] >>> If we must have __aiter__, then we may as well also have __anext__; >>> besides >>> being more consistent, it also allows an object to be both a normol >>> iterator >>> and an asynch iterator. >> >> And this is a good point too. > I'm not convinced that allowing an object to be both a normal and an > async iterator is a good thing. It could be a recipe for confusion. > I doubt that it will be a popular thing. But disallowing this by merging two different protocols in one isn't a good idea either. Yury
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