Yury Selivanov wrote:
Well, using next() and iter() on coroutines in asyncio code is something esoteric. I can't even imagine why you would want to do that.
I'm talking about the fact that existing generator- based coroutines that aren't decorated with @coroutine won't be able to call new ones that use async def.
This means that converting one body of code to the new style can force changes in other code that interacts with it.
Maybe this is not considered a problem, but as long as it's true, I don't think it's accurate to claim "full backwards compatibility".