Hello everyone, For a while now I have been working on potential plans for making Django async-capable, and I finally have a plan I am reasonably happy with and which I think we can actually do.
This proposed roadmap, in its great length, is here: https://www.aeracode.org/2018/06/04/django-async-roadmap/ I'd like to invite discussion on this potential plan - including: - Do we think async is worth going after? Note that this is just async HTTP capability, not WebSockets (that would remain in Channels) - Can we do this in a reasonable timeframe? If not, is there a way around that? - Are the proposed modifications to how Django runs sensible? - How should we fund this? There's many more potential questions, and I really would love feedback on this. I'm personally pretty convinced that we can and should do this, but this is a decision we cannot take lightly, and I would love to hear what you have to say. Andrew -- 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 post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAFwN1up4%2BP%2B4bCSSiG6t845idoM8dvktnuTs4dH2R5aAuCz3iA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
