Move viz stuff to mesa-viz-tornado Git repo

[rht]

No description provided.

[rht]

This greatly simplifies the setup.py, and we should be able to move to setup.cfg+pyproject.toml very soon.

[tpike3]

So my understanding is #1747 fixes the build fails; but what about the lint-ruff fails that the imports are unsorted?

[codecov]

Codecov Report

Patch coverage: 88.88% and project coverage change: +8.31% 🎉

Comparison is base (856d4bc) 72.35% compared to head (f3c4f70) 80.66%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1746      +/-   ##
==========================================
+ Coverage   72.35%   80.66%   +8.31%     
==========================================
  Files          20       15       -5     
  Lines        1302      869     -433     
  Branches      246      183      -63     
==========================================
- Hits          942      701     -241     
+ Misses        325      147     -178     
+ Partials       35       21      -14     

Files Changed	Coverage Δ
mesa/visualization/TextVisualization.py	0.00% <0.00%> (-39.48%)	⬇️
mesa/__init__.py	100.00% <100.00%> (ø)
mesa/visualization/ModularVisualization.py	100.00% <100.00%> (+32.72%)	⬆️
mesa/visualization/UserParam.py	100.00% <100.00%> (ø)
mesa/visualization/__init__.py	100.00% <100.00%> (ø)
mesa/visualization/modules.py	100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rht]

One main blocker to this PR is that the dependencies once again include a Git repo. mesa-viz-tornado needs to be released as a PyPI package first.

[rht]

Another blocker is that the API documentation no longer shows the viz stuff: https://mesa--1746.org.readthedocs.build/en/1746/apis/visualization.html. Either create a separate RTD for mesa-viz-tornado, or just tell people to read the source code directly. Either way, I'd rather spend effort on completing the Solara viz features than on this.

[tpike3]

Just to be overly explicit, the plan is to merge this, but before we do another PyPI release create a mesa-viz-tornado package so the release doesn't break.

As for updates to the RTD, I can work on that, but concur to keep working Solara, based on the feedback we have already received.

[rht]

Either way, I'd rather spend effort on completing the Solara viz features than on this.

This may sound like I'm running away from the responsibility of ensuring that the existing viz API documentation persists. I meant it as prioritization for my time allocation.

[tpike3]

Either way, I'd rather spend effort on completing the Solara viz features than on this.

This may sound like I'm running away from the responsibility of ensuring that the existing viz API documentation persists. I meant it as prioritization for my time allocation.

It doesn't your fine, we are always running on limited bandwidth we have to prioritize and python front end has been our # 1 feedback so Solara has to be the priority