#36919: Allow `TaskResult` (and `Task`) to be pickled
-------------------------------------+-------------------------------------
Reporter: Jake Howard | Owner: Varun
Type: | Kasyap Pentamaraju
Cleanup/optimization | Status: assigned
Component: Tasks | Version: 6.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Varun Kasyap Pentamaraju):
Replying to [comment:3 Jake Howard]:
Hi Jake, I guess Natalia is just suggesting reusing (or taking inspiration
from) some logic inside Serializer, which already converts a function to
its dotted import path and includes validation for non-importable cases.
> I'm not sure I understand where DB serialization comes into this? I
don't think `Task` or `TaskResult` will ever need to be serialized in a
migration (and it's probably an antipattern if they do). It did remind me
of `django.core.serializers`, but that seems focused on the ORM, which I
also don't think is relevant.
--
Ticket URL: <https://code.djangoproject.com/ticket/36919#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019c6b4ff22c-4bf95cc1-fb11-4ab7-8366-e32dfa9a9c7c-000000%40eu-central-1.amazonses.com.
