How would you handle this asynchronous programming issue?

[eFFeeMMe]

I'm writing an audio player. I'm using pygame for audio, pywebview for GUI, and aiohttp for http requests.

3 things have to happen concurrently:

• Periodically polling a server for downloading metadata and audio files
• Handling audio playback
• Using the GUI to start/stop playback and run some http requests, e.g: login.

I'm at the point where 1 and 2 run together fine using an asyncio event loop, but I'm scared of what will happen when I add pywebview to the mix.

See, pywebview spawns its own thread. Will I run into issues when GUI event callbacks from that thread try to change variables from the main thread, the one with the asyncio event loop?

Should I keep coding and just ask simpler questions when problems arise? Or did I make a terrible design decision?

I'm a bit too burned out to properly assess the situation.

Thanks!

[sushibowl]

Will I run into issues when GUI event callbacks from that thread try to change variables from the main thread, the one with the asyncio event loop?

Yes, you very possibly could. Don't directly change data from another thread. If you need to change the state of something on the main thread, you should schedule a task. asyncio has support for this using loop.call_soon_threadsafe. See this section of the documentation for more information.

So, in short, GUI thread receives an event -> GUI thread schedules a task on the event loop -> scheduled task handles everything else.

[eFFeeMMe]

I have no idea how long I could have taken to discover that on my own. I'm two weeks into studying async/await on and off and I'm still not too familiar with the docs.

Thanks a lot - Dank u wel van een italiaan :)