On Sat, Mar 20, 2021 at 7:49 PM Chris Angelico <ros...@gmail.com> wrote:
> On Sun, Mar 21, 2021 at 1:30 PM Yury Selivanov <yselivanov...@gmail.com> > wrote: > > That said I wouldn't mind aiter() supporting the two-arguments mode as > it could make it easier to convert some sync code bases (that use > greenlets, for example) to async. And given that async iteration mirrors > the sync iteration protocol pretty closely, I think that aiter() fully > mirroring iter() is expected. I do realize that my arguments here are weak, > so my vote is +0 to support the two-arguments mode. > > > > I'm -0.5 on two-argument aiter(), mainly because YAGNI. Two-arg iter() > might be worth a single bullet point somewhere in a list of > "translating blocking code to nonblocking". > It was made of one use case: iter(f.readline, ""). -- --Guido van Rossum (python.org/~guido) *Pronouns: he/him **(why is my pronoun here?)* <http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/OZ5RDRDLKKGUDMLD3FJS6IHC76XEG36P/ Code of Conduct: http://python.org/psf/codeofconduct/
