Re: [web2py] Re: Nginx, uwsgi, on Windows

2016-04-21 Thread Kiran Subbaraman
The module (which included grequests) was being used in a web2py and non-web2py context. The grequest capability was coming into play in the latter context. Refactored by separating out this responsibility. Kiran Subbaraman

Re: [web2py] Re: Nginx, uwsgi, on Windows

2016-04-21 Thread Niphlod
why would you use a library made to use gevent in an environment that doesn't support it ? if you need to use gevent-coroutines-etc-etc-etc you need to have the COMPLETE env supporting it, not just a piece. On Thursday, April 21, 2016 at 7:49:25 AM UTC+2, Kiran Subbaraman wrote: > > Narrowed

Re: [web2py] Re: Nginx, uwsgi, on Windows

2016-04-20 Thread Kiran Subbaraman
Narrowed down the issue. Basically, the grequests modules that I was using seems to be the cause of the "LoopExit: This operation would block forever" Create an application: *redis_event* *controller: default.py* import cache_mod def index(): return dict(message=cache_mod.get_value())

Re: [web2py] Re: Nginx, uwsgi, on Windows

2016-04-20 Thread Kiran Subbaraman
Thanks for the recommendation - IIS with web2py is a recommended deployment on Windows. The gevent-mix-up-with-rocket, was based on the stack trace I pasted below. And like I mentioned, this connection was made without any evidence ... so yeah, I was writing this before I gave it too much

[web2py] Re: Nginx, uwsgi, on Windows

2016-04-20 Thread Niphlod
forget about uwsgi on windows. never really landed as production-ready. fortunately iis can run python without any hiccup and it's the current recommended way to deploy web2py in production on windows. that being said, I'm really eager to know how the hell you're getting gevent mixed up with