News for hackers. Stuff that matters.

A comment on Django 3. Parent comment

Re:Django 3 by 904baf11 on Monday December 02, 2019 @11:20AM (#21683804)
It's convuluted, it's not structured concurrency (https://vorpus.org/blog/notes-on-structured-concurrency-or-g...), fundamentally despite being async/await a lot of networking code is based on callbacks anyway (see: asyncio.Protocol), and I've had a lot of trouble debugging code that spawn tasks because asyncio code has zero obligation to care about any of the tasks it spawns.
[ Parent | on HN ]
Re:Django 3 by tomchristie on Tuesday December 03, 2019 @02:54PM (#21696023)
Yo. Two points here.

* You can absolutely stay within structured concurrency constraints using ASGI.

* The ASGI spec doesn’t have anything to do with asyncio. It’s purely an async/await interface - You can build against it just fine using other concurrency backends.

[ Parent | on HN ]