pyodide-test-runner naming

Currently, we have the pyodide-test-runner package which exposes both the tools to run Pyodide in Node and browsers from host Python and pytest fixtures. Other relevant use case is running Pyodide from Python are,

• sandboxed code execution
• CLI applications using Pyodide, possibly related to what Hood is experimenting with

we essentially already have the code to make it possible and I wonder if it would be better to have, a) a pyodide-test-runner package (current situation) and tell people to either use this or create their own if they want to run in WASM from Python b) have a separate - pyodide-runner package to run code in Pyodide from Python + possible some CLI related tools - pytest-pyodide package (following the convention for pytest plugins) with the pytest related hooks and fixtures (which would depend on pyodide-runner)

No strong opinion. WDYT @hoodmane @ryanking13 ?

In any case, we should decide this before we upload the package to PyPi https://github.com/pyodide/pyodide/issues/2741

[rth]

I’ll let you push the current contents

Actually, since I have time to work on this now, I can do it and put you as the commit author.

[ryanking13]

Thanks for working on that! I think the top priority is to take off initialize_global_hiwire_objects from the test package so that we can update Pyodide API without modifying the pytest-pyodide.

Opened a PR about this #2889