Myles Scolnick

I was thinking the notebook author could be explicit at the top of their wasm notebooks: ```python import micropip await micropip.install("https://raw.githubusercontent.com///path/to/pkg.whl") import my_package ``` We would just need to have...

Yep, this looks good. It would be nice if CI could publish the whl back into `main`. Maybe fine for now.

In the meantime, you can do this: ```python from sympy import latex import marimo as mo def print_sympy(obj): return mo.md(f""" \[ {latex(obj)} \] """) ``` Playground: https://marimo.app/l/n2kkic

@agostof - your patch is quite nice if you or @kamyuen or anyone else wants to make a contribution to the repo - you can add this to `marimo/_output/formatters`

Can you include more information such as running "marimo env"

Hi, we've launched a new VSCode extension at https://github.com/marimo-team/marimo-lsp ([readme](https://github.com/marimo-team/marimo-lsp/tree/main/extension)). It may mean this issue is resolved or no longer applicable. If the issue still exists, please file the issue...

@Eloitor you could again use `mo.state` and track the selection and put up a warning (`mo.callout`) when there is an invalid selection

Yes, this is not entirely a bug. `python-lsp-server.` must be installed in the same venv. This is so it can pick up any customizations we provide and use the correct...

@bulletmark I would not recommend installing marimo with `uv tool install`. You are likely using a different `venv` when you start marimo up.

@bulletmark I see, thanks for investigating that. we likely don't fetch the package dependecies (or fetch different ones) when on the home page