-
Notifications
You must be signed in to change notification settings - Fork 152
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
Upgrade to Django 4.2 raises new warning #531
Comments
Is your project public, or do you have some minimal code to reproduce the issue? |
https://github.com/paperless-ngx/paperless-ngx. |
Are you serving your app with |
|
|
Ah, that would do it. Thanks! |
You're welcome. I guess we could close this issue? |
It might be better to remain open, linked to be closed with #359, if it can ever merge. Others will probably be seeing it soon enough as they upgrade. |
I understand that WhiteNoise does not yet support ASGI, but I would like to better understand whether this warning is critical (this will break something or severely impact performance) or if it's minor. I'm seeing guides that both recommend WhiteNoise and recommend running with ASGI (e.g., this guide from Render). Is this a reasonable default for a new application? |
This issue is caused by a lack of ASGI support within WhiteNoise, For those looking for ASGI support, see |
Python Version
3.11.5
Django Version
4.2.5
Package Version
6.5.0
Description
After upgrading a project from Django 4.1.9 to Django 4.2.5, there is a new warning in my application logs:
After some work and adding some patching, the response in this case is a
WhiteNoiseFileResponse
. As far as I can tell, everything works correctly, but it would be nice to not have this warning, without silencing it myself.The text was updated successfully, but these errors were encountered: