How to try a pre-release/development version locally wi...

At a glance

The post discusses an issue with the Marimo package, where it installs the version from PyPI that corresponds to the running version, making it difficult to test development branches. The community members tried installing the dev branch directly in the notebook, but that didn't work either.

In the comments, the community members discuss potential solutions, such as commenting out a section of code to install an editable version of Marimo, and using importlib.metadata to check if the package is being installed in an editable mode. They eventually find a solution using distribution.origin in Python 3.13, which is demonstrated in a pull request.

Useful resources

ggabriel

From the logs that flash by as marimo starts in sandbox mode, it seems it installs the version of the marimo package from pypi that corresponds to the running version's version. This works fine with official releases, but makes it hard to test development branches, since they still have the prior version number, so the running notebook won't reflect the changes

I tried installing the dev branch of marimo that I wanted to try from within the notebook itself, but that didn't work either:

11 comments

ggabriel

cross-posted here with more details: https://discord.com/channels/1059888774789730424/1254862968068243476/threads/1332190342228742224

MMyles Scolnick

i dont think there is a great way to do this. i've commeneted out this in the code to test this. you can kinda trick the code path with MARIMO_MANAGE_SCRIPT_METADATA=true marimo edit, but that wont actually create the sandbox for you (just think you are in one).

MMyles Scolnick

i have this code:

Plain Text

    marimo_deps = [d for d in dependencies if _is_marimo_dependency(d)]
    if not marimo_deps:
        # During development, you can comment this out to install an
        # editable version of marimo assuming you are in the marimo directory
        # DO NOT COMMIT THIS WHEN SUBMITTING PRs
        # return dependencies + [f"marimo -e ."]

        return dependencies + [f"marimo=={marimo_version}"]

MMyles Scolnick

if there is a way to check if you are running from an editable install, that would help. or we could expose an environment variable

ggabriel

thanks for the follow-up! looks like this is exposed by importlib metadata

ggabriel

it's a little roundabout for now:

Plain Text

import json
from importlib.metadata import Distribution

direct_url = Distribution.from_name("pkg-name").read_text("direct_url.json")
pkg_is_editable = json.loads(direct_url).get("dir_info", {}).get("editable", False)

ggabriel

apparently with python 3.13 you can just directly access distribution.origin

ggabriel

got this info from here:
https://github.com/pypa/setuptools/issues/4186#issuecomment-1893322635

MMyles Scolnick

ah very cool, let me try it out

MMyles Scolnick

it works! https://github.com/marimo-team/marimo/pull/3568

ggabriel

awesome! thanks!

Add a reply

Get help from the marimo community

How to try a pre-release/development version locally with sandbox?