Hey everyone, Sorry if I'm not following correct protocol on this or if this has already been discussed elsewhere, but is there any consensus about (or needed for) creating async versions of contrib packages?
My personal interest in this is about django.contrib.auth (login, authenticate, etc.) and django.contrib.syndication (views.Feed) but I would guess this sort of work would fall under a general policy. I read DEP009 <https://github.com/django/deps/blob/main/accepted/0009-async.rst> and didn't see any discussion of this topic, nor could I find any discussions on the ticket tracker (my skills using the tracker are limited). I could only find 2 files mentioning "async" in django/contrib/ (git grep "async" django/contrib | grep "\.py:"): * django/contrib/contenttypes/fields.py (added by me recently <https://github.com/django/django/commit/7b94847e384b1a8c05a7d4c8778958c0290bdf9a>, a bug fix <https://code.djangoproject.com/ticket/34139>) * django/contrib/staticfiles/handlers.py (added as part of standing up async support <https://github.com/django/django/commit/a415ce70bef6d91036b00dd2c8544aed7aeeaaed> ) Has there been any consensus about this? If I'm interested in async versions of functions/features in contrib packages should I just file tickets, or is this something that might need a DEP first? Again, sorry if I'm barking up the wrong tree. It's not my intention to waste anyone's time! -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/70e80f26-e1fa-4aa9-a3a8-0d7dc38752c3n%40googlegroups.com.
