web2(3)py builds "on-top" of things: taking a not-finished library as something that can change from time to time basically leads to "if tulip dies so does web2(3)py". So, until it's committed to python stable, noone would pickup that as a base reference to build a framework.
Benoitc is the author of gunicorn, that works yet and pretty awesomely without hiccups. As things stand, there are a very few places in which web2(3)py needs improvement to support "the async way". All the blockings are circumventable with web2(3)py as it is running inside an evented environment, and leveraging specific "async-friendly" drivers for the db interaction. If the issue is "choose a different standard webserver than rocket", we tried not so long ago to review all the possible options, but at the time being there's no python webserver capable of doing everything cherrypy or rocket do, so it would cripple a lot of installation environments. That being said, if something that builds on top of tulip comes up and supports wsgi, it can be easily added to anyserver.py. -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
