Right: I could give you a recipe that tells you to first create a Python virtual environment, then install mlx-vlm, then make sure to downgrade to numpy 1.0 because some of the underlying libraries don't work with numpy 2.0 yet...
... or I can give you a one-liner that does all of that with uv.
python-specific side question -- is there some indication in the python ecosystems that Numpy 2x is not getting adoption? numpy-1.26 looks like 'stable' from here
I think it's just that it's a breaking change to a fundamental library, so it will take many months for the ecosystem to upgrade.
Similar thing happened when Pydantic upgraded from 1 to 2.
I have a project on torch 2.6 and numpy 2.2. I never had any issues with that combination.