Desktop toys python code#
Desktop toys python mac#

RT jeremyphoward: Wow what an interesting new kaggle competition! Or maybe not interesting: like lots of academic projects that talk about reproducibility, I don't actually see anytвЂ¦ /i/web/status/1вЂ¦ 9В hoursВ ago

Desktop toys python code#

How easy would it be to take one or other of those components to create an electron app bundled with a py/jupyter server that could support live code execution from the Jupyer Book also inside the electron app?

I wonder if the JupyterLab-app, and or the datasette-app, have elecron+py components cleanly separated from the app code components. That post also briefly also explored the possibility of providing live code execution via a thebe connected local server, as well as mooting the possibilty of executing the code via pyodide. PS whilst tinkering with the fragment describing a Jupyter Book Electron App, I wrapped a Jupyter book in an electron app to remove the need for a web server to serve the book. HmmвЂ¦ I wonderвЂ¦ the jupyter-server/jupyter_releaser package looks to be providing support for automating builds and release generators for templated Jupyter projectsвЂ¦ How tightly are apps bound into electron packages? How easy would it be to have a releaser to wrap an app in an electron package with a specfied conda distribution (an вЂњelectron-py-app proxyвЂќ into which you could drop your jupyter framework app?) HmmвЂ¦ thinksвЂ¦ did I also see somewhere discussion about a possible JuypterLite app that would use WASM kernels rather than eg bundling conda or accessing local Jupyyter servers? And I wonderвЂ¦ how much of the JupyterLab-App repo could be lifted and used to directly wrap RetroLab? Or maybe, the JupyterLab app could have a button to switch to RetroLab view, and vice versa? I also wonder: as the electron app bundles conda, could it also ship postgres as a callable database inside the app? Postgres is available via conda, after all.

Desktop toys python mac#

(For a related discussion on signing Mac apps, see TIL tale, вЂњSigning and notarizing an Electron app for distribution using GitHub ActionsвЂќ and this related JupyterLab-app issue.)

Wrong! -)Д«ut a handy startвЂ¦ and possibly a useful way of shipping simple environments to students, at least, once the signing issues are fixed. Not only are the workspaces messing each other up, but it means not only that the same notebook is open in two environments (causing write conflicts) but those environments are also using different kernels for the same notebook.

I also note that if I open several notebooks in the app, then in my browser launch a new JupyterLab session, the open notebooks in the app appear as open notebooks in the browser JupyterLab UI: so workspaces are shared? That really really sucks. Something else that might be handy would be the ability to connect to a remote server and launch a remote kernel, or launch and connect to a MyBinder kernelвЂ¦