Should Django Revisit Type Annotations for New Code Like DEP-14?

It’s hard to believe, but it’s been almost 5 years since the Django community and technical board weighed in on adding types to Django. Here was the board’s statement: https://groups.google.com/g/django-developers/c/C_Phs05kL1Q/discussion

Although I, like many others, disagreed with that decision, their ruling was final at the time. However, the typing community has made enormous progress since then, and tools like django-stubs have greatly improved my codebases while mypy has become more expressive.

Now, I propose that we revisit this decision for new code. For example, DEP-14—adding background tasks—presents a prime opportunity. @theorangeone has done an incredible job on a fully typed reference implementation, which I use daily in production. See here: https://github.com/RealOrangeOne/django-tasks

This implementation includes complete type annotations, even for dynamic arguments in functions like enqueue. The value here is significant: proper typing can even help enforce constraints such as forbidding non-serializable arguments using a JSON type.

It would be unfortunate to strip these types from such a valuable PR. Could we consider leaving the type annotations intact?