-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Open
@AamodThakur
Description
Your current environment
Hi,
vllm installation is getting stucked due to "numba" package.
Collecting numba==0.61 (from vllm) Using cached numba-0.61.0.tar.gz (2.8 MB) Preparing metadata (setup.py) ... error error: subprocess-exited-with-error ▒ python setup.py egg_info did not run successfully. ▒ exit code: 1 ▒▒> [18 lines of output] Traceback (most recent call last): File "<string>", line 2, in <module> exec(compile(''' ~~~~^^^^^^^^^^^^ # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<32 lines>... exec(compile(setup_py_code, filename, "exec")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ''' % ('/tmp/pip-install-67eioooo/numba_1f494ef99f254895b4ed3a8e0621bb4d/setup.py',), "<pip-setuptools-caller>", "ex ec")) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^ File "<pip-setuptools-caller>", line 35, in <module> File "/tmp/pip-install-67eioooo/numba_1f494ef99f254895b4ed3a8e0621bb4d/setup.py", line 51, in <module> _guard_py_ver() ~~~~~~~~~~~~~^^ File "/tmp/pip-install-67eioooo/numba_1f494ef99f254895b4ed3a8e0621bb4d/setup.py", line 48, in _guard_py_ver raise RuntimeError(msg.format(cur_py, min_py, max_py)) RuntimeError: Cannot install on Python version 3.14.0; only versions >=3.10,<3.14 are supported. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: metadata-generation-failed ▒ Encountered error while generating package metadata. ▒▒> See above for output. note: This is an issue with the package mentioned above, not pip.
We have tried installing "pip install numba==0.63.0b1" which is python3.14 supported but vllm is fixed at older numba version and not considering newer version.
Thanks
How you are installing vllm
pip install vllm
Before submitting a new issue...
- Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.