#31380: Deploy system check that DJANGO_ALLOW_ASYNC_UNSAFE is not set
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: hashlash
Johnson |
Type: New feature | Status: assigned
Component: Utilities | Version: 3.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by hashlash):
* owner: nobody => hashlash
* needs_docs: 0 => 1
* has_patch: 0 => 1
* status: new => assigned
Comment:
Replying to [comment:6 Adam (Chainz) Johnson]:
> I think we want to avoid 'asyncio' since that's a specific library, and
in theory async stuff can move to other async libraries like curio / trio.
Maybe 'asgi' is a better tag, since that's the target framework for django
async stuff. Or we could use `async_ = 'async'` as the tag, acknowledging
it's a reserved word.
I'll take `asgi` and will make the PR. Tell if anybody has any thoughts
about the naming
--
Ticket URL: <https://code.djangoproject.com/ticket/31380#comment:7>
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/068.d8360cd5a8694cdf77bdbb931674d68e%40djangoproject.com.
