bdfb065b5d
### What this PR does / why we need it?
1. Enable pymarkdown check
2. Enable python `__init__.py` check for vllm and vllm-ascend
3. Make clean code
### How was this patch tested?
- vLLM version: v0.9.2
- vLLM main:
29c6fbe58c
---------
Signed-off-by: wangli <wangli858794774@gmail.com>
28 lines
1.1 KiB
Markdown
28 lines
1.1 KiB
Markdown
<!-- Thanks for sending a pull request!
|
|
|
|
BEFORE SUBMITTING, PLEASE READ https://docs.vllm.ai/en/latest/contributing/overview.html
|
|
|
|
-->
|
|
### What this PR does / why we need it?
|
|
<!--
|
|
- Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue.
|
|
If possible, please consider writing useful notes for better and faster reviews in your PR.
|
|
|
|
- Please clarify why the changes are needed. For instance, the use case and bug description.
|
|
|
|
- Fixes #
|
|
-->
|
|
|
|
### Does this PR introduce _any_ user-facing change?
|
|
<!--
|
|
Note that it means *any* user-facing change including all aspects such as API, interface or other behavior changes.
|
|
Documentation-only updates are not considered user-facing changes.
|
|
-->
|
|
|
|
### How was this patch tested?
|
|
<!--
|
|
CI passed with new added/existing test.
|
|
If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future.
|
|
If tests were not added, please describe why they were not added and/or why it was difficult to add.
|
|
-->
|