#33716: async middleware can be a regular function too
-------------------------------+--------------------------------------
Reporter: abetkin | Owner: nobody
Type: New feature | Status: new
Component: Uncategorized | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by abetkin):
* status: closed => new
* type: Bug => New feature
* resolution: invalid =>
Comment:
Okay, this is expected behavior and not a bug. I propose to remove this
restriction for middleware when you have to handle sync and async cases
separately. Because the middleware often does not contain any I/O
--
Ticket URL: <https://code.djangoproject.com/ticket/33716#comment:15>
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/01070180d67c8db1-fd550356-0ed1-4b39-8507-19afc6393aa1-000000%40eu-central-1.amazonses.com.
