As far as I got from the internet, the async/await
stuff is a sort of paradigm enrichment of the python ecosystem.
One can now access a for of concurrent execution thanks to an event loop. Much like in the browser.
I'm ok with that, but I don't really get how to bridge what one knows from the classic synchronous execution workflow,
so I experimented a bit. The async_iter_over_tcp.py
is just a playground that can be invoked like this (ITER_TIMES
defaults to 5):
$ ITER_TIMES=10 python async_iter_over_tcp.py
To raise the log level there is the LOG_LVL
variable:
$ LOG_LEVE=DEBUG python async_iter_over_tcp.py