building @marimo.io; prev @harvard.edu
we're also integrating managed sandboxed environments for PEP 723 notebooks, powered by uv ofc. forget venvs
we're also integrating managed sandboxed environments for PEP 723 notebooks, powered by uv ofc. forget venvs
@marimo.io. no more dir() / help()-ing around `
@marimo.io. no more dir() / help()-ing around `
add/remove/upgrade deps the uv way — no more flat pip-style lists or accidentally pip-ing your env
add/remove/upgrade deps the uv way — no more flat pip-style lists or accidentally pip-ing your env
what’s frustrated you about using packages in notebooks?
what’s frustrated you about using packages in notebooks?
gist.github.com/manzt/1ca8f8...
gist.github.com/manzt/1ca8f8...
wild how as portable binary, everything you need to be productive with ~Python~… can be accessible from ~JavaScript~ ecosystem (npm/pnpm/bun/deno/yarn). No extra install necessary:
wild how as portable binary, everything you need to be productive with ~Python~… can be accessible from ~JavaScript~ ecosystem (npm/pnpm/bun/deno/yarn). No extra install necessary:
turns out there’s some neat public works history hiding in there. maybe you’ll find an (CC0!) upgrade for that default OS wallpaper 🙃
turns out there’s some neat public works history hiding in there. maybe you’ll find an (CC0!) upgrade for that default OS wallpaper 🙃
tooling lets us write plenty of code that no JS runtime could ever execute, and it leads to a ton of indirection and misunderstanding for beginners.
tooling lets us write plenty of code that no JS runtime could ever execute, and it leads to a ton of indirection and misunderstanding for beginners.
it detects notebooks with PEP 723 metadata and prompts you to create/sync a venv. you can manage deps directly in the notebook toolbar to author standalone notebooks of your own:
it detects notebooks with PEP 723 metadata and prompts you to create/sync a venv. you can manage deps directly in the notebook toolbar to author standalone notebooks of your own:
type assertions (`foo as string`) blindly tell the type checker you know more than it does. `assert` is a real runtime check with the same narrowing effect. you'll thank me later when debugging!
type assertions (`foo as string`) blindly tell the type checker you know more than it does. `assert` is a real runtime check with the same narrowing effect. you'll thank me later when debugging!
just pipe the data into a new `Response`:
just pipe the data into a new `Response`:
```
juv venv --from=Untitled.ipynb
or
juv venv --from=foo.py
```
and select the `.venv` in your editor.
```
juv venv --from=Untitled.ipynb
or
juv venv --from=foo.py
```
and select the `.venv` in your editor.