RetroSearch Browse

Sat May 2 11:15:48 CEST 2015 · https://mail.python.org/pipermail/python-dev/2015-May/139778.html

On 1 May 2015 at 21:27, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
> 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.

I having been arguing for merging two different protocols.  I'm saying
that allowing an object to be both normal and async iterable is not an
argument for having separate protocols because it's not a good thing.

Cheers,

-- 
Arnaud

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-May/139778.html below:

[Python-Dev] PEP 492: async/await in Python; version 4