Chris Angelico <ros...@gmail.com>: > On Sun, Sep 10, 2017 at 8:08 PM, Marko Rauhamaa <ma...@pacujo.net> wrote: >> What's more, when you turn a function into an async, you need to >> refactor a large part of your program. > > That's not Python-specific. If you're going to change your program > from single-threaded single-process synchronous to any of > multi-threaded, multi-process, or asynchronous (all of which involve > multiple pieces running concurrently or interleaved), you have to > build your program with that in mind. It's best NOT to try to convert, > but to build it that way from the start. Give threaded socket servers > a try - you'll learn a lot. It's really not hard.
It's not Python-specific but it *is* async-specific. Multithreading, multiprocessing and callback hell don't result in similar cascading effects. Even otherwise, I'm not at all convinced by the whole coroutine concept. Marko -- https://mail.python.org/mailman/listinfo/python-list
