Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

django-after-response works with runserver and gunicorn, but not with uwsgi #8

Open
lduros opened this issue Jun 21, 2016 · 1 comment

Comments

@lduros
Copy link

lduros commented Jun 21, 2016

I haven't been able to get any threading.Thread to work with uwsgi, including when using the django-after-response decorators. Has anyone experienced the same problem? I've actually written a more detailed explanation on stackoverflow: http://stackoverflow.com/questions/37930268/differences-between-uwsgi-and-gunicorn-when-running-async-calls

Thanks,

@lduros lduros changed the title django-after-response works with runserver and unicorn, but not with uwsgi django-after-response works with runserver and gunicorn, but not with uwsgi Jun 21, 2016
@fletchowns
Copy link

Looks like your stackoverflow post was resolved. Solution was to add --enable-threads to your uWSGI config. Sounds like this ticket can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants