> It seems like having a whole framework/ecosystem for loop lifecycle management, async libs, state/comm, etc will unfortunately be needed.
... 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
... 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