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'm curious about how this differs from aiosqlite. Is it mainly the optional compatibility with trio, or are there other advantages it offers? If so, it might be worth adding a sentence or two about that to the Readme!
Over in aiohttp-client-cache, I've had a few frustrations with aiosqlite, mainly because of its Connection object also being a Thread (see: 187, 189). TL;DR, I'm mainly wondering if the threads managed by anyio are any easier to work with than plain stdlib Thread objects.
The text was updated successfully, but these errors were encountered:
The only difference is that if your Connection is also a Thread, you would manage all of that Thread staff manually, which could cause issues like this whereas in anysqlite, all of that staff is managed by the anyio package, which would not cause your programm to hang indefinitely.
I'm curious about how this differs from aiosqlite. Is it mainly the optional compatibility with trio, or are there other advantages it offers? If so, it might be worth adding a sentence or two about that to the Readme!
Over in aiohttp-client-cache, I've had a few frustrations with aiosqlite, mainly because of its
Connection
object also being aThread
(see: 187, 189). TL;DR, I'm mainly wondering if the threads managed by anyio are any easier to work with than plain stdlibThread
objects.The text was updated successfully, but these errors were encountered: