Hi LLaVA-NeXT team,
I recently encountered issues when using lmms-eval where manual cloning and installation of this repository was required.
It would be extremely helpful if LLaVA-NeXT could be published to PyPI (e.g., as pip install llava-next). This would allow downstream projects (like lmms-eval) to list it as a dependency, automating the installation process and ensuring version reproducibility.
Even if the import name remains llava, having a distributable package on PyPI would significantly improve the developer experience.
Thank you for your great work!
Hi LLaVA-NeXT team,
I recently encountered issues when using
lmms-evalwhere manual cloning and installation of this repository was required.It would be extremely helpful if LLaVA-NeXT could be published to PyPI (e.g., as
pip install llava-next). This would allow downstream projects (likelmms-eval) to list it as a dependency, automating the installation process and ensuring version reproducibility.Even if the import name remains
llava, having a distributable package on PyPI would significantly improve the developer experience.Thank you for your great work!