added bitsandbytes dependency in common requirement.txt file

[dipatidar]

FILL IN THE PR DESCRIPTION HERE

FIX #5503

BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

---

PR Checklist (Click to Expand)

Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.

PR Title and Classification

Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

• [Bugfix] for bug fixes.
• [CI/Build] for build or continuous integration improvements.
• [Doc] for documentation fixes and improvements.
• [Model] for adding a new model or improving an existing model. Model name should appear in the title.
• [Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
• [Kernel] for changes affecting CUDA kernels or other compute kernels.
• [Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
• [Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
• [Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.

Code Quality

The PR need to meet the following code quality standards:

• We adhere to Google Python style guide and Google C++ style guide.
• Pass all linter checks. Please use format.sh to format your code.
• The code need to be well-documented to ensure future contributors can easily understand the code.
• Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
• Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes

Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.

What to Expect for the Reviews

The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

• After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
• After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
• After the review, the reviewer will put an action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
• Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You

Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only trigger fastcheck CI to run, which consists only a small and essential subset of tests to quickly catch errors with the flexibility to run extra individual tests on top (you can do this by unblocking test steps in the Buildkite run).

Full CI run is still required to merge this PR so once the PR is ready to go, please make sure to run it. If you need all test signals in between PR commits, you can trigger full CI as well.

To run full CI, you can do one of these:

• Comment /ready on the PR
• Add ready label to the PR
• Enable auto-merge.

🚀

[dipatidar]

/ready

[mgoin]

We have bnb as an optional dependency intentionally at the moment. Is there strong justification to include it?
If we do want to include it, then it should not be in common dependencies since it is specific to the CUDA backend (as of now).

[rkooo567]

+1. Let's make sure to minimize necessary requirements if possible

[sd109]

As far as I can tell, if bitsandbytes is omitted from the common dependencies then it ends up being missing from the vllm-openai Docker image. Is this a strong enough justification to include it in the common requirements? Or at least in the CUDA requirements?

[simon-mo]

Please feel free to add it here

vllm/Dockerfile

Lines 204 to 205 in 3724d5f

	RUN --mount=type=cache,target=/root/.cache/pip \
	pip install accelerate hf_transfer 'modelscope!=1.15.0'

Our general policy is to avoid installing to much as default pip dependency, but the docker image can be optimized to work out of the box.

[dipatidar]

The problem is with source installation of vllm. In the docker container we use, the vllm installation done using pip install -e. With installation I get ModuleNotFoundError: No module named 'bitsandbytes' File "/opt/conda/envs/vllm/lib/python3.11/site-packages/vllm/model_executor/layers/quantization/bitsandbytes.py", line 128, in __init__ raise ImportError("Please install bitsandbytes>=0.42.0 via " ImportError: Please install bitsandbytes>=0.42.0 via pip install bitsandbytes>=0.42.0 to use bitsandbytes quantizer. Where do you suggest to add bitsandbytes in this case?

[russellb]

Please feel free to add it here

vllm/Dockerfile

Lines 204 to 205 in 3724d5f

	RUN --mount=type=cache,target=/root/.cache/pip \
	pip install accelerate hf_transfer 'modelscope!=1.15.0'

Our general policy is to avoid installing to much as default pip dependency, but the docker image can be optimized to work out of the box.

This was implemented in #8792, so I think this PR can now be closed.