Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to run Schelling experimental - jupyter_viz not found #145

Closed
jackiekazil opened this issue Jul 29, 2024 · 6 comments
Closed

Unable to run Schelling experimental - jupyter_viz not found #145

jackiekazil opened this issue Jul 29, 2024 · 6 comments

Comments

@jackiekazil
Copy link
Member

jackiekazil commented Jul 29, 2024

I am getting the following error while trying to run examples/schelling_experimental :

from mesa.visualization.jupyter_viz import JupyterViz, Slider, make_text
ModuleNotFoundError: No module named 'mesa.visualization.jupyter_viz'

Steps to recreate:

  • Setup new env
  • in the examples/schelling_experimental. Run:
    pip install -r requirements
  • run solara run app.py, error appears during the loading process.
@jackiekazil
Copy link
Member Author

@rht, I haven't had a chance to dig into this. Am I imagining that worked on something relating to this recently? Wondering if something minor didn't get updated in versions or if this is a bigger issue?

@EwoutH
Copy link
Member

EwoutH commented Jul 29, 2024

What Python and Mesa versions are reported?

@rht
Copy link
Contributor

rht commented Jul 29, 2024

It is mesa~=2.0. It is due to this PR https://github.com/projectmesa/mesa-examples/pull/128/files, which forgot to update to the latest 'pre' version for the requirements.txt.

@EwoutH
Copy link
Member

EwoutH commented Jul 29, 2024

So it should work on the latest pre-release / git main.

This is another argument why we need a monorepo (see projectmesa/mesa-geo#212 (review)).

@rht
Copy link
Contributor

rht commented Jul 29, 2024

This is another argument why we need a monorepo (see projectmesa/mesa-geo#212 (review)).

Breaking changes are supposed to be a rare event. This class of errors (of this GH issue) should not have happened that often.

@jackiekazil
Copy link
Member Author

jackiekazil commented Jul 29, 2024

That resolved the issue.

RE: mono repo - the argument against it was that examples were not easily discoverable to people less familiar with repository structures. Originally the examples were in the main repo.

Unless we explicitly have an action here, I am going close and consider this "resolved" with the next deployment, which I believe will occur soon with recent conversations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants