1 May
2015
1 May
'15
8:27 p.m.
On 2015-05-01 4:24 PM, Arnaud Delobelle wrote:
On 1 May 2015 at 20:24, Yury Selivanov
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