to be honest, it works wonderfully for the original intent which was to use JS on main and Pyodide in workers + it works just fine for primitives but it annoys me in Python it doesn't ... I might try to patch that myself with a wrapper main only but the sync is the first thing that needs to exist and I wouldn't know the best approach to do so but I'll think about it. There is a draft PR though so we can track progress: pyscript/polyscript#170

I'm now working on isolating my approach to Python-to-Python calls to a separate project I would be able to show.
Maybe it would be useful to somebody.

@WebReflection Did it! https://github.com/jolaf/workerlib

lovely! just a few thoughts:

• this is pyodide only, for what I could tell, I think that should be specified?
• is this published on pip and, if not, wouldn't be great to have it as remote package ?

with GitHub pages, hosting something publicly is really simple, I'd give it a try!

name = "workerlib"

# files are resolved relatively to this config URL
[files]
"./workerlib.py" = ""

save that as workerlib.toml, as example, create github pages for the root of your project and you'll have https://jolaf.github.io/workerlib/ website out of your README that will offer the ability to run that package with ease through remote_packages entry ... worth a shot?

this is pyodide only, for what I could tell, I think that should be specified?

Yeah, definitely.

is this published on pip

Not yet, but I'll probably try it later.

wouldn't be great to have it as remote package ?

Hmm, great idea! I'll try, thanks!

Thanks for review!! :)