Best practice to only include pyodide-py in non-emscripten environments

[CNSeniorious000]

I have a package which currently depends on pyodide/pyodide-py's pyodide.code.eval_code_async. But there is no need to install pyodide-py in emscripten runtime. So I need to specify it in pyproject.toml.

So which one is better?

[project]
dependencies = [
  "pyodide-py~=0.26.0a4 ; platform_system != 'Emscripten'",
]

Or

[project]
dependencies = [
  "pyodide-py~=0.26.0a4 ; sys_platform != 'emscripten'",
]

[hoodmane]

They are both very idiomatic, it probably doesn't matter which one. We are thinking about renaming the platform to pyodide fyi.

[hoodmane]

Nevermind about platform renaming.

[ryanking13]

Just curious, in which place do you use pyodide-py in your package? We publish pyodide-py mostly for typing and it is not recommended to use it in other places.

[hoodmane]

And eval_code_async can return the last expression's return value, so we choose this over builttins' eval.

I was just arguing that this should be added to the Python stdlib @brandtbucher @ambv. But we should definitely factor CodeRunner, eval_code_async, etc into a separate package. Whenever someone gets time to do that, I've been thinking about it for several years now.

[hoodmane]

Okay, turns out PyPI makes you set up two factor authentication if you want to upload a package manually.

[hoodmane]

Uploaded here:
https://github.com/pyodide/coderunner
https://pypi.org/project/useful-coderunner/

[hoodmane]

Interestingly, hatchling tagged the wheel py2.py3 even though I gave it a requires_python of 3.10.

[CNSeniorious000]

It's only a typos mistake in pyproject.toml