You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found this post because I don't get the appeal of async-await, but definitely have some issues with database io via Django for which i'm trying to find a solution, and async - other than breaking everything - would be one route to a fix.
What is it about async code that couldn't be accomplished better by a Python runtime mode/flag that handles the boundaries where blocking calls occur in an async "style" that jumps to other unblocked code inside an internally-managed event-loop? (and then extend that mechanism so C-level python extensions can handle async dispatch too.)
This AST parsing to solve the maintenance burden of double async+sync functions is the logical endpoint for the situation we have found ourselves in. But - and I ask in this odd forum because you are the person who wrote exactly this kind of code - why are we here? Legit: what am I missing about async/await that means we actually needed to bifurcate so much code?
Automatic async to sync code conversion — Psycopg
Python adapter for PostgreSQL
https://www.psycopg.org/articles/2024/09/23/async-to-sync/
The text was updated successfully, but these errors were encountered: