#31380: Deploy system check that DJANGO_ALLOW_ASYNC_UNSAFE is not set
-------------------------------------------------+------------------------
Reporter: Adam (Chainz) Johnson | Owner: nobody
Type: New feature | Status: new
Component: Utilities | Version: 3.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-------------------------------------------------+------------------------
Django's async-safety feature disable itself if the environment variable
DJANGO_ALLOW_ASYNC_UNSAFE is set to any value. This is useful for jupyter
notebooks and similar, however it can lead to data loss in production.
I suggest a deploy-tagged system check that returns an error if it is set,
to guard against it being used for production web traffic.
--
Ticket URL: <https://code.djangoproject.com/ticket/31380>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.6128163a15739cd83d8916687d5521d5%40djangoproject.com.
