On Sun, Mar 21, 2021 at 1:30 PM Yury Selivanov <[email protected]> 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". ChrisA _______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/3CXVPF44ZDQDSS77JJRCMLUVNPLZ3KJ7/ Code of Conduct: http://python.org/psf/codeofconduct/
