run any of these parts from a thread where there is a running event loop, you will get a SynchronousOnlyOperation error. Note that you don’t have to be inside an async function directly to have this error request to make sure the socket is closed cleanly. ## SynchronousOnlyOperation ## exception SynchronousOnlyOperation[source] The SynchronousOnlyOperation exception is raised when code that is only allowed from async code before, this may trigger if you were doing it incorrectly. If you see a SynchronousOnlyOperation error, then closely examine your code and move any database operations to be in a synchronous

code - it will block up the event loop (or, more likely, Django will notice and raise a SynchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django’s asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside a separate run any of these parts from a thread where there is a running event loop, you will get a SynchronousOnlyOperation error. Note that you don’t have to be inside an async function directly to have this error

code - it will block up the event loop (or, more likely, Django will notice and raise a SynchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django's asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside a separate run any of these parts from a thread where there is a running event loop, you will get a SynchronousOnlyOperation error. Note that you don’t have to be inside an async function directly to have this error

code - it will block up the event loop (or, more likely, Django will notice and raise a SynchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django's asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside a separate run any of these parts from a thread where there is a running event loop, you will get a SynchronousOnlyOperation error. Note that you don’t have to be inside an async function directly to have this error

code - it will block up the event loop (or, more likely, Django will notice and raise a SynchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django's asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside a separate run any of these parts from a thread where there is a running event loop, you will get a SynchronousOnlyOperation error. Note that you don’t have to be inside an async function directly to have this error

code - it will block up the event loop (or, more likely, Django will notice and raise a SynchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django's asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside a separate run any of these parts from a thread where there is a running event loop, you will get a SynchronousOnlyOperation error. Note that you don’t have to be inside an async function directly to have this error

code - it will block up the event loop (or, more likely, Django will notice and raise a SynchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django's asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside a separate run any of these parts from a thread where there is a running event loop, you will get a SynchronousOnlyOperation error. Note that you don’t have to be inside an async function directly to have this error

code - it will block up the event loop (or, more likely, Django will notice and raise a SynchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django’s asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside run any of these parts from a thread where there is a running event loop, you will get a SynchronousOnlyOperation error. Note that you don’t have to be inside an async function directly to have this error

code - it will block up the event loop (or, more likely, Django will notice and raise a synchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django's asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside

code - it will block up the event loop (or, more likely, Django will notice and raise a synchronousOnlyOperation to stop that from happening). Fortunately, you can do many queries using Django's asynchronous supported with asynchronous queries and updates. You will find that trying to use one raises SynchronousOnlyOperation. If you wish to use a transaction, we suggest you write your ORM code inside