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 just started looking at flet recently to help me build a mobile app for my ham radio library APRSD. It makes heavy use of threads to process packets. Looking at the the 1.0 documentation it looks like flet has made the decision to double down on asyncio, which creates lots of problems for apps/libraries that make use of threads. I had to completely rewrite the tcp kiss client from scratch to get rid of asyncio as it caused no end of problems working with threads. I find this dissapointing to move to a wholy asyncio mechanism especially since python itself is getting rid of the GIL, therefore making threading even more attractive.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I just started looking at flet recently to help me build a mobile app for my ham radio library APRSD. It makes heavy use of threads to process packets. Looking at the the 1.0 documentation it looks like flet has made the decision to double down on asyncio, which creates lots of problems for apps/libraries that make use of threads. I had to completely rewrite the tcp kiss client from scratch to get rid of asyncio as it caused no end of problems working with threads. I find this dissapointing to move to a wholy asyncio mechanism especially since python itself is getting rid of the GIL, therefore making threading even more attractive.
asyncio = pain and suffering.
Beta Was this translation helpful? Give feedback.
All reactions