-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable mypy type checking #3680
Comments
The current remaining
and misc after |
For those who are new to the vLLM repo, determining the correct type of each variable is a great way to enhance your understanding of how the code is connected together. |
Quick update on the latest progress:
However, the effectiveness of type checking is still quite minimal because imported types are currently treated as Lines 46 to 51 in 2be6955
My IDE, which uses Pyright basic mode, still flags a lot of errors, showing that there is much work to be done. Moving forward, we should work on gradually applying |
Cool, looking forward to the progress. |
This is a great issue to improve the code quality of the repo, so please feel free to work on it if anyone is interested! One example PR in the past #4043 |
I'm taking a crack at vllm/core, just to get my feet wet with the codebase. |
There are errors indicating incompatibilities between
An example of the error:
|
I have been working on this for the past few days. Stay tuned for updates! |
Opened #7248. |
Was going to take a crack at |
Resolve mypy warnings under `vllm/entrypoints` and turn on `mypy` checks for this directory in `format.sh` and in CI. part of issue vllm-project#3680 Signed-off-by: Russell Bryant <[email protected]>
Enable `mypy` checks on `vllm/inputs` and add some casts to fix the warnings present for this directory. Part of issue vllm-project#3680 Signed-off-by: Russell Bryant <[email protected]>
Anything you want to discuss about vllm.
Even though vLLM is type annotated but we did not enable type checking. It would be useful to add it, even incrementally.
The text was updated successfully, but these errors were encountered: