#31793: Async management command support
-------------------------------------+-------------------------------------
Reporter: James Pic | Owner: nobody
Type: New feature | Status: closed
Component: Core (Management | Version: 3.0
commands) |
Severity: Normal | Resolution: wontfix
Keywords: assync | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hi James. There's a fundamental difference between middlewares, which sit
squarely on the request-response pathway, and **need** to be async capable
if we're to leverage the full potential of that, on the one hand, and
management commands, which are called one-by-one from the command line
most usually, on the other. A management can **use** async code, in which
can `asyncio.run()` is fine, but there's no demonstrated need for the top-
level `handle()` entry point to itself be async capable. There's no
concurrency need for management commands. ("Au contraire mon ami" -- fine,
use multiprocessing if you insist, but there's nothing that's worth adding
complexity to the main entry point here for.)
--
Ticket URL: <https://code.djangoproject.com/ticket/31793#comment:5>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.a31be46a84e5267113b595d9fdd084e7%40djangoproject.com.
