current PyScript events https://docs.pyscript.net/2024.8.2/faq/#pyscript-events

That's a good solution! I don't mind if the logging keeps happening on the console.

to provide more context loadPackage callbacks don't get propagated to micropip so that's a dead-end to know what's going on when you have packages around, as those callbacks would never tell you anything micropip is doing or signaling while bootstrapping (cc @hoodmane) ... I ended up mokey-patching temporarily the console.log while bootstrapping to be able to actually fetch all those logs nobody asked for or can easily hook into and the result is actually looking pretty good.

Events are triggered on the main thread even from workers so there is no disambiguation needed: you listen to py:progress event on the page, you get what you asked for ... as example, this is having matplotlib as package and all events appended to the body before a print(sys.version) (from a worker, which dispatches on the main ... it works on main too):

How did you patch console.log? I've attempted to set window.console = myConsole in a <script> loading before all of them, but this wasn't enough to intercept the calls from WASM.

it's always a hack to patch globals so I am not super happy to share the how because if done in a bad way everything else would break but the nitty gritty is that you don't reassign window console, you overload console.log and friends but be sure to put back the original version or bad things could happen.

I think we can close this as it's landing within the next release (soon)