|
|
|
|
|
|
by Goopplesoft
3339 days ago
|
|
|
There will be interesting community impacts from python's asyncio -- I'd venture its going to create a lot of fragmentation in the realtime application ecosystem. The issue seems to be that there isn't an agreed way to consume derivative apis as the flow control and interfaces around asyncio are super clunky. Further, the all-or-nothing nature of asyncio (don't block the thread) means a significant portion of applications will have to have some rewrite to support asyncio (webframeworks, sqlalchmy and such). There are already two fairly large ecosystems around asnycio network libs + http frameworks which are large rewrites of existing libraries (https://github.com/klen/muffin and https://github.com/aio-libs). It seems like having a whole framework/ecosystem for loop lifecycle management, async libs, state/comm, etc will unfortunately be needed. I hope we find a way to work around this although I doubt there is a good way. |
|
|
... twisted has been around for ages for exactly this reason as a 'framework' unfortunately this means it's not 100% ported to python3 yet, but I suspect (not a dev, etc) that as twisted becomes more mature and 2.x dies off, there might be more overlap between these two things.. and perhaps other similar projects