3 ms·
Another project I'd fund: Making Django an async-first (not async-only) framework over the next decade. It's easier to mix sync code into async than the other w
by miiiiiike 2y ago
Another project I'd fund: Making Django an async-first (not async-only) framework over the next decade. It's easier to mix sync code into async than the other way around.
- zzzeek 2y agoSo glad that's not actually true so I didn't have to rewrite sqlalchemy from scratch
- miiiiiike 2y agoIt's more straightforward to call a sync function from an async function than the other way around. That's a pretty uncontroversial statement. Adding async support to a library doesn't mean starting starting over. I'm not fully understanding your thought. Can you say more?
- JodieBenitez 2y agoIf one can make it without breaking the API too much, why not. The #1 reason I use Django is stability. I have projects that span 4 major Django version without any significant break. That's quite a feature.