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
Created https://github.com/django/django/pull/11917
This patch will print the results of the query (if it has been evaluated).
I did hit one odd case while writing the tests. Essentially, if you do:
queryset = SomeModel.objects.all()
list(queryset)
SomeModel.objects.create(...)
repr(queryset)
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
On Tue, Oct 15, 2019, at 9:45 AM, Josh Smeaton wrote:
> A co-worker just linked me to
>
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 wrote:
>
Week ending October 13, 2019.
*Triaged*:
https://code.djangoproject.com/ticket/30845 - Simple explanation of default
app folder structure. (invalid)
https://code.djangoproject.com/ticket/30844 - Add after_db_init() hook
method to model (wontfix)
https://code.djangoproject.com/ticket/30843 - New
We've made the second release on the way to Django's next major
release, Django 3.0! With a month and a half until the final release,
we'll need timely testing from the community to ensure a stable
release. Check out the blog post:
Wow... Good news.
On Mon, Oct 14, 2019 at 4:38 PM Mariusz Felisiak
wrote:
> We've made the second release on the way to Django's next major
> release, Django 3.0! With a month and a half until the final release,
> we'll need timely testing from the community to ensure a stable
> release. Check
