Skip to content

Conversation

princepride
Copy link
Contributor

@princepride princepride commented Jun 12, 2025

Purpose

Fix #19432

Test Plan

Run the command:

uv venv -p 3.9 --seed
source .venv/bin/activate
uv pip install -U vllm \
    --torch-backend=auto \
    --extra-index-url https://wheels.vllm.ai/nightly
# vllm==0.9.1rc2
vllm serve facebook/opt-125m --port 30303
curl http://localhost:30303/v1/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{"model": "facebook/opt-125m", "prompt": "Say this is a test", "temperature": 0, "max_tokens": 7}'

Test Result

Check the python version and start the server:

Screenshot 2025-06-12 at 7 40 12 PM Screenshot 2025-06-12 at 7 40 37 PM

Execution result:

Screenshot 2025-06-12 at 7 41 02 PM

Signed-off-by: 汪志鹏 <[email protected]>
Copy link

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @princepride, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a compatibility issue with Python 3.9 by conditionally applying the strict=True argument to the zip function call. This allows the vLLM worker components to function correctly in environments running Python versions older than 3.10, specifically targeting the reported issue in Python 3.9.

Highlights

  • Python Version Compatibility: Added conditional logic to handle the strict argument of the zip function, which was introduced in Python 3.10. This ensures compatibility with Python 3.9 environments.
  • Code Location: The fix is applied in the _update_states method within both the GPU and TPU model runner files.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@mergify mergify bot added v1 tpu Related to Google TPUs labels Jun 12, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly addresses the TypeError encountered with zip(..., strict=True) on Python 3.9 by introducing a version check for sys.version_info >= (3, 10). For older Python versions, zip is now called without the strict argument.

A key consideration is that the strict=True parameter in zip (for Python 3.10+) ensures that an error is raised if the zipped iterables have different lengths. By falling back to a non-strict zip for older versions, this explicit check is lost, and zip will silently truncate to the length of the shorter iterable. My main feedback is to suggest adding a manual length check in the else blocks for both modified files to maintain the original strict behavior and prevent potential silent errors if the iterable lengths are not guaranteed to be identical.

Signed-off-by: 汪志鹏 <[email protected]>
Signed-off-by: 汪志鹏 <[email protected]>
Signed-off-by: 汪志鹏 <[email protected]>
Copy link
Member

@DarkLight1337 DarkLight1337 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for fixing!

@DarkLight1337 DarkLight1337 enabled auto-merge (squash) June 12, 2025 15:07
@github-actions github-actions bot added the ready ONLY add when PR is ready to merge/full CI is needed label Jun 12, 2025
Copy link
Member

@njhill njhill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @princepride and sorry for introducing this incompatibility.

IMO though it would be better to just remove the strict=True for now. It's just a conservative check and not worth this amount of extra code/complexity.

@princepride
Copy link
Contributor Author

Thanks @princepride and sorry for introducing this incompatibility.

IMO though it would be better to just remove the strict=True for now. It's just a conservative check and not worth this amount of extra code/complexity.

@DarkLight1337 What do you think of this suggestion? By the way, the unit test failed, it seems that it is not a problem with my code

@DarkLight1337
Copy link
Member

Yeah I'm fine with removing strict=True

Signed-off-by: 汪志鹏 <[email protected]>
auto-merge was automatically disabled June 13, 2025 03:29

Head branch was pushed to by a user without write access

Signed-off-by: 汪志鹏 <[email protected]>
@DarkLight1337 DarkLight1337 merged commit cefdb99 into vllm-project:main Jun 13, 2025
64 checks passed
Copy link
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready ONLY add when PR is ready to merge/full CI is needed tpu Related to Google TPUs v1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Python 3.9 compat: TypeError: zip() takes no keyword arguments

3 participants