#36816: Allow **kwargs in @task decorator to support custom Task subclasses
-----------------------------+------------------------------------
Reporter: Pietro | Owner: (none)
Type: New feature | Status: new
Component: Tasks | Version: 6.0
Severity: Normal | Resolution:
Keywords: task | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by Jake Howard):
* stage: Unreviewed => Accepted
Comment:
This sounds like a reasonable change to me.
As for the solution, my suggestion would be to drop all explicit
arguments, and only accept `**kwargs` in the `@task` decorator - instead
moving the defaults to the `Task` class itself. That also means that, for
whatever reason, a custom `Task` can override defaults.
--
Ticket URL: <https://code.djangoproject.com/ticket/36816#comment:6>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019b47fdf951-2fb6023a-ae66-41f7-b1ff-563fe1b5579e-000000%40eu-central-1.amazonses.com.
