This session is part of the mainters track. Recently it became possible to run Python and the scientific Python packages in the browser thanks to WebAssembly and [Emscripten](https://emscripten.org/). This is done in particular in the [Pyodide](https://github.com/pyodide/pyodide) and [emscripten-forge](https://github.com/emscripten-forge/recipes) projects. It allows for a scientific Python application, or a compute environment such as [JupyterLite](https://github.com/jupyterlite/jupyterlite), to be seamlessly accessible to a large number of users with very little effort or infrastructure requirements. At the same time, the scientific Python ecosystem did not evolve with the web in mind. We will discuss some of the challenges package maintainers may face when trying to run their package in the browser, and what could be done to overcome these.
Recently it became possible to run Python and the scientific Python packages in the browser thanks to WebAssembly and [Emscripten](https://emscripten.org/). This is done in particular in the [Pyodide](https://github.com/pyodide/pyodide) and [emscripten-forge](https://github.com/emscripten-forge/recipes) projects. It allows for a scientific Python application, or a compute environment such as [JupyterLite](https://github.com/jupyterlite/jupyterlite), to be seamlessly accessible to a large number of users with very little effort or infrastructure requirements. At the same time, the scientific Python ecosystem did not evolve with the web in mind. We will discuss some of the challenges package maintainers may face when trying to run their package in the browser, and what could be done to overcome these.
Speakers: Roman Yurchak Thorsten Beier