Replies: 2 comments
-
Hm, it could be kind of tricky I guess. I've checked Trio docs and it uses its own synchronization primitives (Lock, channels instead of queues?) as well as classes to work with TCP and files. It means re-implementing portions of Flet internals for each async backend, right? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Honestly I don't look at Flet code (how yoy handle the async stuff), but it will probably requires a bit of effort, but anyio is pretty straightforward and is compatible with asyncio and trio |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello everyone,
I saw this article presenting async support for Flet apps. This is great! Thank you for all your effort.
My proposition is to give the ability to users to select other async backends than asyncio. I'm thinking of trio and anyio leveraging structured concurrency.
The idea will be to run the app with something like the following:
Beta Was this translation helpful? Give feedback.
All reactions