Django 3.0 Release Notes - ASGI

[Josh Smeaton]

A co-worker just linked me to https://docs.djangoproject.com/en/dev/releases/3.0/#asgi-support and asked me (basically) if we can start doing all kinds of async work in one of our projects. Unfortunately, I didn't really know how to answer.

Preface: I haven't followed the ASGI plan very closely (I read the DEP and have a vague understanding of the vision).

It's my understanding that there's only very limited support for ASGI, and most features of Django won't work properly when running under ASGI. But that's not clear from reading the release notes or the deploy on ASGI section of the docs. Should we have a section in the docs that show what is and is not supported, along with examples?

It'd be good to have a spot in the docs to point to that shows what is in and out of scope for each milestone.

Thoughts?

[Markus Holtermann]

Good point, Josh.

I think we should either add an "experimental" note to the ASGI notes or introduce an "Experimental changes" section (I'm open to other naming suggestions)

/Markus

> --
> 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-develop...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/9b11ecd8-997f-4edc-a627-5523da611a55%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/9b11ecd8-997f-4edc-a627-5523da611a55%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Andrew Godwin]

I agree - we need to communicate that ASGI support does not mean you can start writing async def views. I think we should put a big disclaimer to that effect next to it in the release notes and say it should be coming next release.

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-develop...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9b11ecd8-997f-4edc-a627-5523da611a55%40googlegroups.com.

[Josh Smeaton]

Sorry to resurrect this thread, and to ask and not do, but there have been a few questions on this ML about async support, and I imagine there'd be a few over on django-users too.

I've created https://code.djangoproject.com/ticket/31182#ticket to track this. 

On Tuesday, 15 October 2019 15:15:46 UTC+11, Andrew Godwin wrote:

I agree - we need to communicate that ASGI support does not mean you can start writing async def views. I think we should put a big disclaimer to that effect next to it in the release notes and say it should be coming next release.

Andrew

On Mon, Oct 14, 2019 at 5:45 PM Josh Smeaton <josh....@gmail.com> wrote:

A co-worker just linked me to https://docs.djangoproject.com/en/dev/releases/3.0/#asgi-support and asked me (basically) if we can start doing all kinds of async work in one of our projects. Unfortunately, I didn't really know how to answer.

Preface: I haven't followed the ASGI plan very closely (I read the DEP and have a vague understanding of the vision).

It's my understanding that there's only very limited support for ASGI, and most features of Django won't work properly when running under ASGI. But that's not clear from reading the release notes or the deploy on ASGI section of the docs. Should we have a section in the docs that show what is and is not supported, along with examples?

It'd be good to have a spot in the docs to point to that shows what is in and out of scope for each milestone.

Thoughts?

--
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-d...@googlegroups.com.