[Python-ideas] Learning from the shell in supporting asyncio background calls

[Jonathan Slenders]

> "I think python's non blocking I/O is far from being something useful for
> developers till non-async code can invoke async code transparently.
> Duplicating all code/libs when you realize that something not fits asyncio
> is not a solution and even less a pythonic solution."


About this. I think I absolutely understand the difficulties, but in
reality the "problem" is broader.
Code is always written using certain paradigms. And Python allows a lot of
these, so depending on the background, use case and interests of the
author, he decides what paradigm to use. These days, we have functional
code, reactive code, imperative, declarative, object oriented,
event-driven, etc...
All paradigms have different answers to questions like "Where do we keep
our state?" (the variables), "Where do we do our I/O?", "how do we reuse
our code?", "how do we write our logic?".

Not everything is compatible. Mixing two styles can sometimes be very ugly
and confusing. I guess the question is more about finding the right glue to
put things together, without forcing code to fit into another paradigm.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20150812/852cd3a9/attachment-0001.html>