asgiref 3.3.2 introduced stricter checks for what an async function is, so I would imagine that's the problem. 3.3.3 fixes some of them, but I'm guessing you might have a different flavour of problem.
Could you get the traceback out of Django that's causing the 500 error and post it here?
Andrew
On Tue, Apr 6, 2021, at 9:56 AM, kradem wrote:
Thank you very much for a quick response.Yes, that's the problem:asgiref 3.3.2When I downgrade it to 3.3.1 Django complains ("django 3.2 requires asgiref<4,>=3.3.2, but you have asgiref 3.3.1 which is incompatible."), but static files are served well.I tried with the very last version 3.3.3 (-e git+https://github.com/django/asgiref.git#egg=asgiref), but problem hasn't been fixed that way.Dana utorak, 6. travnja 2021. u 17:46:31 UTC+2 korisnik Andrew Godwin napisao je:This may be related to https://github.com/django/asgiref/issues/251 - what version of asgiref are you running?AndrewOn Tue, Apr 6, 2021, at 9:43 AM, kradem wrote:> 500 Internal Server Error> Exception inside application.
> DaphneThis error raises every time a file from static folder is accessed.What would be a proper way for debugging this? I've got "justMyCode": false setting in VS Code and that doesn't catch anything.Python 3.9.2channels 3.0.3daphne 3.0.1Django 3.2
--You received this message because you are subscribed to the Google Groups "Django users" group.To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9db2fc19-e87c-4a69-ab9e-6c53ec56d6fcn%40googlegroups.com.
--You received this message because you are subscribed to the Google Groups "Django users" group.To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/5c9ffb1b-c644-41c6-a5c3-a52bb95a1893n%40googlegroups.com.
No comments:
Post a Comment