Unfreeze tasks class

[codingjoe]

Code of Conduct

• I agree to follow Django's Code of Conduct

Feature Description

Unfreezing tasks can improve versatility for custom task implementations and subclasses. Tasks are instantiated during module loading as quasi singletons. People can better use inheritance or even do in-place updates with decorators. Attribute read performance could be improved by slotting them.

Problem

Based on this forum discussion: https://forum.djangoproject.com/t/tasks-framework-versatility-performance/45035

TL;DR: Frozen dataclasses can't be easily modified during runtime. This is extra true for decorators. A practical example from django-crontask was that I wanted to attach the schedule to a task instance while being task backend/task agnostic.

cc @RealOrangeOne

Request or proposal

proposal

Additional Details

No response

Implementation Suggestions

While freezing task results makes sense architecturally (even though they are updated in place via refresh) the same argument doesn't extend to Task singletons. Freezing only makes it harder for people to go wild and build amazing things. :)

[github-actions]

Thank you codingjoe for sharing your idea! We have a lot of them so please be patient. You can see the current queue here.

Community instructions

For commenters, please use the emoji reactions on the issue to express support, and/or concern easily. Please use the comments to ask questions or contribute knowledge about the idea. It is unhelpful to post comments of "I'd love this" or "What's the state of this?"

Reaction Guide

• 👍 This is something I would use
• 👎 This is something that would cause problems for me or Django
• 😕 I’m indifferent to this
• 🎉 This is an easy win