Forcing the user to handle it doesn't add any benefits, though. If someone calls a task with a UUID, and receives a string, that's a surprise to them. It's also not a surprise any type checker will detect. The problem isn't the serializing, it's the lack of type-consistent deserialization on the other end.

If the queue store has a task with arguments ['2025-02-11 14:56:15.896305'], it passes it through to the task as a string. Which might be right, if the user passed it as a string (as they would have to now), but may also be incorrect if they passed a datetime which was transparently converted to a string, since there's no deterministic way to do the conversion the other way.

If the user needs to handle the deserialization, why not let them handle the serialization, too, and avoid any potential foot-guns.

Use DjangoJSONEncoder when serializing JSON #134

Description

Activity

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions