Why I built this. In my work I make a lot of little tools and they all end up as spreadsheets. Spreadsheets are fine but the UI is limiting. I wanted real apps a non-technical person can just open and use, without standing up a server or making an account. So I borrowed the spreadsheet model and ran with it. Free and open source, because I like making things that help people.
getvessel.dev
Since a .vessel can carry code someone else wrote, isolation was the main thing I designed around. Each one runs sandboxed and can only reach the network origins it declares up front. Your data stays a plain SQLite file too. Unzip a .vessel and you can open the database in any SQLite tool. Nothing locked away.
getvessel.dev
#localfirst #selfhosted #privacy #sqlite #python #pyodide #ai #opensource
A bit on how Vessel works under the hood. The Python backend runs under Pyodide in a Web Worker, so there's genuinely no server in the loop. The worker can't even open a socket. The UI talks to FastAPI through a fetch bridge, and SQLite rides along inside the file. All local, all offline.
getvessel.dev
#pyodide #python #webassembly #sqlite #opensource #localfirst
I made a thing called Vessel. A .vessel is a single file holding an app's whole UI, a Python (FastAPI) backend, and an SQLite database, with the data living right inside the file. You install a small host once, then any .vessel opens locally and runs like a normal app. Think of it like a spreadsheet, except the document is a real web app instead of a grid!
pyodide est un portage de l'interpréteur Python en webassembly, qui permet donc de faire tourner du code écrit en Python dans le navigateur, code qui a accès à toute l'API web du navigateur.
Avec l'acceptation de la PEP 783, il est désormais possible de publier sur PyPI des paquets construits pour PyOdide : https://blog.pyodide.org/posts/314-release/.
Michel Caradec nous avait parlé de PyOdide dans son intervention "Python loin de ton ordinateur" : https://youtu.be/Dzjjwhx2Amk?list=PLv7xGPH0RMUT1GSCGHJmqnswpk-nyz5aq&t=1129
We are pleased to announce the Pyodide 314.0 release. This release focuses on standardization and packaging, marking a significant milestone in the Python-in-the-browser ecosystem. PEP 783 is Accepted: What Does It Mean? The acceptance of PEP 783: Emscripten packaging marks perhaps the most exciting change in the history of the Python-in-the-browser ecosystem. Pyodide maintainers—especially @hoodmane—have poured an immense amount of effort into this over a very long time. Achieving this long-standing goal will expand our ecosystem exponentially.
We are pleased to announce the Pyodide 314.0 release. This release focuses on standardization and packaging, marking a significant milestone in the Python-in-the-browser ecosystem. PEP 783 is Accepted: What Does It Mean? The acceptance of PEP 783: Emscripten packaging marks perhaps the most exciting change in the history of the Python-in-the-browser ecosystem. Pyodide maintainers—especially @hoodmane—have poured an immense amount of effort into this over a very long time. Achieving this long-standing goal will expand our ecosystem exponentially.
We are pleased to announce the Pyodide 314.0 release. This release focuses on standardization and packaging, marking a significant milestone in the Python-in-the-browser ecosystem. PEP 783 is Accepted: What Does It Mean? The acceptance of PEP 783: Emscripten packaging marks perhaps the most exciting change in the history of the Python-in-the-browser ecosystem. Pyodide maintainers—especially @hoodmane—have poured an immense amount of effort into this over a very long time. Achieving this long-standing goal will expand our ecosystem exponentially.
Pyodide 314.0: Python packages can now publish WebAssembly wheels to PyPI
https://blog.pyodide.org/posts/314-release/
#HackerNews #Pyodide #WebAssembly #Python #PyPI #314.0 #development
We are pleased to announce the Pyodide 314.0 release. This release focuses on standardization and packaging, marking a significant milestone in the Python-in-the-browser ecosystem. PEP 783 is Accepted: What Does It Mean? The acceptance of PEP 783: Emscripten packaging marks perhaps the most exciting change in the history of the Python-in-the-browser ecosystem. Pyodide maintainers—especially @hoodmane—have poured an immense amount of effort into this over a very long time. Achieving this long-standing goal will expand our ecosystem exponentially.
If y'all would indulge me a late addition: the appropriate lines in the #RDKit code (https://github.com/rdkit/rdkit/blob/master/rdkit/Chem/Draw/__init__.py#L190-L224) can of course be modified to use the B&R blob I introduced in the essay.
What's hampering me from actually trying this out for myself is that due to RDKit not yet being supported by #Pyodide, a lot of the webservices that can run #Python from the browser (e.g. the online version of #jupyter) are also not able to load RDKit. (I have seen at least two proposals to use the JS version of RDKit instead, but I have not managed to make that work either.) Because I had written that essay, and am currently writing this toot from a smartphone (for a number of reasons, I don't have access to a computer I can use), indirectly using RDKit through Wolfram Cloud (basically the online version of Mathematica) is pretty much how I attempt to do cheminformatics experiments on a smartphone. :)
Jack
Python Rennes
GripNews
N-gated Hacker News
Hacker News
𝓙. 𝓜.
Arthur Amalvy