Provide pyodide packages

[twiecki]

Description

Would be great if we could pip install pytensor on pyodide. We can build without the cython extension and it works, however, we should create proper pyodide packages https://pyodide.org/en/0.19.1/development/new-packages.html.

[lucianopaz]

@twiecki, the pypi workflow already builds wheels and uploads them to pypi. Maybe the issue is that you need a special kind of wheel build for pyodide? I don't really know how that works, but I'll edit this issue's title accordingly

[twiecki]

They need to be non-binary / universal as I found out. But apparently this isn't possible with extensions...

[twiecki]

OK, removing the Extension in setup.py allowed me to build a universal wheel:

    setup(
        name=NAME,
        version="2.11.2", #versioneer.get_version(),
        cmdclass=versioneer.get_cmdclass(),
        #ext_modules=[
        #    Extension(
        #        name="pytensor.scan.scan_perform",
        #        sources=["pytensor/scan/scan_perform.pyx"],
        #        include_dirs=[numpy.get_include()],
        #    ),
        #],
    )

And then:
python setup.py bdist_wheel --universal
Followed by twine upload dist/pytensor-2.11.2-cp310-cp310-macosx_11_0_arm64.whl.

Would be nice to somehow automate that process, easiest would be a separate setup.py that doesn't have the Extension (which is optional in Python mode).

But with this, we get native PyMC running in the browser:

[lucianopaz]

Did you just upload a universal wheel to PYPI and not to test-pypi? This is bad and we shouldn't do it. Wheels will always have precedence over source distributions. We build and supply wheels for some platforms and OS versions. If a user is using a different version of the OS or a different platform, calling pip install will grab the wheel, which will not include the compiled extensions! That means that said users will end up with an incomplete installation (it looks like they might be missing the scan with the C linker?). I strongly prefer them to get the full package but compiling it from source. That means that we should remove the universal wheel you added as soon as possible, so that users don't get faulty installations.

[twiecki]

@lucianopaz Thanks for pointing that out, I deleted the wheel. Any idea for how to get non-binary wheels for pyodide only then?

[lucianopaz]

This seems to have the instructions for building the pyodide package. I've never used it, but they say that they have a toolchain that could build the js stuff for us. I have no idea where it gets uploaded afterwards.

[twiecki]

OK, building a proper pyodide package from the source you pointed to seems like the proper way to go. I gave it an honest effort but failed to make pyodide (pyodide/pyodide#3829).

[twiecki]

OK, while I got a pyodide package to work, there is no way to serve it, so we can't pip install it. So universal wheels is the easiest and most user-friendly way to go.

I actually don't think that having non-binary wheels up on PyPI is a big deal. By default, the binary versions will get installed, and where that's not the case, the user gets a big fat warning. wdyt @lucianopaz?

[twiecki]

Oh, we can also just add the cython-compiled c-file to the package as well, so it's actually not an issue! I'm going to re-upload the universal wheel, I don't think there's anything that will break.

[ricardoV94]

@twiecki shall we close this issue or is there stuff we could/should do still?

[twiecki]

I think this would still be useful to have.