Converting to juypter doesn't display in output of notebook

[sherodtaylor]

Describe the bug

After exporting to jupyter notebook running markdown or any other output doesn't display in notebook.

Also if you try to do mo.output.append it throws a no context error. I'd like to be able to convert to a jupyter notebook book for a regularly scheduled report my company uses.

Environment

{
  "marimo": "0.6.19",
  "OS": "Darwin",
  "OS Version": "23.5.0",
  "Processor": "arm",
  "Python Version": "3.11.6",
  "Binaries": {
    "Browser": "126.0.6478.63",
    "Node": "v20.10.0"
  },
  "Requirements": {
    "click": "8.1.7",
    "importlib-resources": "missing",
    "jedi": "0.19.1",
    "markdown": "3.6",
    "pymdown-extensions": "10.8.1",
    "pygments": "2.17.2",
    "tomlkit": "0.12.5",
    "uvicorn": "0.30.1",
    "starlette": "0.37.2",
    "websockets": "12.0",
    "typing-extensions": "4.9.0",
    "black": "24.4.2"
  }
}

Code to reproduce

import marimo

__generated_with = "0.6.19"
app = marimo.App()


@app.cell
def __():
    import marimo as mo

    mo.md("""
    output should display in ipython
    """)
    return mo,


@app.cell
def __(mo):
    mo.output.append(mo.md("hello"))
    return


if __name__ == "__main__":
    app.run()

[mscolnick]

I am converting this to a discussion, as it's not quite an issue for us.

marimo is not built on top of Jupyter so I wouldn't expect it to run in Jupyter at all if you are using the marimo library (import marimo as mo). The marimo library is very integrated with the marimo kernel - which allows us to do a lot of cool things that Jupyter otherwise cannot: reactive ui elements, interpolated markdown, lazy-loading, layouting, streaming outputs, etc.

In order to improve upon the notebook and not be help back by legacy features, technologies, or specs, it is a non-goal to allow the marimo library import marimo as mo to full work inside of Jupyter.

[sherodtaylor]

i agree with the premise of not fully supporting output but why support exporting as a feature if it can't run. Maybe it shouldn't be a bug but semi-feature to allow more people to migrate off of it.

i agree you shouldn't couple it to jupyter but it would be trivial enough to support writing the output or ipython display
it actually does run to some extent it would be nice if you supported a basic output

you could literally just check if it is running in a juypter notebook and call ipython display under the hood.

https://stackoverflow.com/questions/15411967/how-can-i-check-if-code-is-executed-in-the-ipython-notebook

[akshayka]

@sherodtaylor

you could literally just check if it is running in a juypter notebook and call ipython display under the hood.

We'd welcome a pull request for that. We're not intentionally not supporting things. Just limited on time.

[sherodtaylor]

thats fair i just thought i'd raise this as it advertises convert from and to jupyter notebooks.

[mscolnick]

Printing to ipython will likely create more bugs than solve. For example, printing a slider will just return a non-working slider that doesn't update any downstream code. Our tables and charts use some semi-fancy lazy-loading for performance, so that would need to be ported over as well.

why support exporting as a feature

I agree with this sentiment, and it makes it feel like the export is half-done. I think adding some level out python outputs to jupyter will make this feel similarly half-done (i.e. no interactions work, design is off, etc)

We did this originally because it is a respected format that can serve as a bridge to other systems or CLIs (GitHub previews, pandoc, myst, jupytext, etc). For example, marimo export ipynb > some_other_cli

[sherodtaylor]

it doesn't work. It just prints the object and not the generated html

[mscolnick]

including when using matplotlib.pyplot and seaborn?

[sherodtaylor]

@mscolnick actually just checked it is outputting it correctly it's only when using mo.as_html or mo.md

[sherodtaylor]

^ i haven't found a way to get the raw html from the mo.Html object.

[akshayka]

@sherodtaylor, use the text attribute: https://docs.marimo.io/api/html.html#marimo.Html.text