vLLM does not have a direct dependency on numpy, this is required for dependencies of vLLM, i.e. an indirect dependency. We need to wait for the open-source community to adopt numpy 2.0 first, only after that can we safely remove the constraint.

this is entirely confusing, e.g. pixi complains about vllm being the reason

  × failed to solve the pypi requirements of 'ray' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ╰─▶ Because vllm>=0.6.0 depends on numpy<2.0.0 and numpy==2.1.2, we can conclude that vllm>=0.6.0 cannot be used.
      And because only the following versions of vllm are available:
          vllm<=0.6.0
          vllm==0.6.1
          vllm==0.6.1.post1
          vllm==0.6.1.post2
          vllm==0.6.2
          vllm==0.6.3
          vllm==0.6.3.post1
      and you require vllm>=0.6.0, we can conclude that your requirements are unsatisfiable.

vLLM does not have a direct dependency on numpy, this is required for dependencies of vLLM, i.e. an indirect dependency. We need to wait for the open-source community to adopt numpy 2.0 first, only after that can we safely remove the constraint.

@youkaichao this is false (or I misunderstand you) - see

@chris-aeviator I added this line to prevent numpy 2.0 . see #5582 (comment)

Hi @youkaichao, the issue with Outlines was fixed in its 0.1.6 release ~1.5 months ago, see dottxt-ai/outlines#1265. According to the discussion in gh-5582, I think you can remove the pin now.