xc-llm-ascend/pyproject.toml

[build-system]
# Should be mirrored in requirements.txt
requires = [
    "cmake>=3.26",
    "decorator",
    "numpy<2.0.0",
    "packaging",
    "pip",
    "pybind11",
    "pyyaml",
    "scipy",
    "setuptools>=64",
    "setuptools-scm>=8",
    "torch_npu",
    "torch >= 2.5.1",
    "torchvision<0.21.0",
]
build-backend = "setuptools.build_meta"
[Misc] version control by setuptools_scm (#21) make package version control by setuptools_scm to keep the same with vllm Signed-off-by: wangxiyuan <wangxiyuan1007@gmail.com> 2025-02-10 09:36:09 +08:00			`[build-system]`
			`# Should be mirrored in requirements.txt`
			`requires = [`
[core] Support custom ascendc kernels in vllm-ascend (#233) This PR add custom ascendc kernel rotary_embedding support in vllm-ascend, related CMakeLists and setuptools is also added in this PR. Related: https://github.com/vllm-project/vllm-ascend/issues/156 --------- Signed-off-by: ganyi <pleaplusone.gy@gmail.com> 2025-04-03 14:52:34 +08:00			`"cmake>=3.26",`
[Misc] version control by setuptools_scm (#21) make package version control by setuptools_scm to keep the same with vllm Signed-off-by: wangxiyuan <wangxiyuan1007@gmail.com> 2025-02-10 09:36:09 +08:00			`"decorator",`
Set numpy < 2.0.0 to resolve numpy VersionConflict (#476) ### What this PR does / why we need it? vLLM bumps numpy version to 2.x: https://github.com/vllm-project/vllm/commit/8427f70493ed67bf26cb9e7fa98ac202b991c37d , this will cause a `pip._vendor.pkg_resources.ContextualVersionConflict: (numpy 2.2.4 (/usr/local/python3.10/lib/python3.10/site-packages), Requirement.parse('numpy==1.26.4'), {'vllm-ascend'})` failure when vllm ascend install. This PR resolved the issue by: - Set numpy < 2.0.0 to resolve numpy VersionConflict - Sync requirements and toml - Reorder ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? CI passed Closes: https://github.com/vllm-project/vllm-ascend/issues/473 Signed-off-by: Yikun Jiang <yikunkero@gmail.com> 2025-04-07 16:07:21 +08:00			`"numpy<2.0.0",`
[MISC] Add patch module (#526) This PR added patch module for vllm 1. platform patch: the patch will be registered when load the platform 2. worker patch: the patch will be registered when worker is started. The detail is: 1. patch_common: patch for main and 0.8.4 version 4. patch_main: patch for main verison 5. patch_0_8_4: patch for 0.8.4 version 2025-04-16 09:28:58 +08:00			`"packaging",`
[CI] enable custom ops build (#466) ### What this PR does / why we need it? This PR enable custom ops build by default. ### Does this PR introduce _any_ user-facing change? Yes, users now install vllm-ascend from source will trigger custom ops build step. ### How was this patch tested? By image build and e2e CI --------- Signed-off-by: wangxiyuan <wangxiyuan1007@gmail.com> 2025-04-12 10:24:53 +08:00			`"pip",`
Set numpy < 2.0.0 to resolve numpy VersionConflict (#476) ### What this PR does / why we need it? vLLM bumps numpy version to 2.x: https://github.com/vllm-project/vllm/commit/8427f70493ed67bf26cb9e7fa98ac202b991c37d , this will cause a `pip._vendor.pkg_resources.ContextualVersionConflict: (numpy 2.2.4 (/usr/local/python3.10/lib/python3.10/site-packages), Requirement.parse('numpy==1.26.4'), {'vllm-ascend'})` failure when vllm ascend install. This PR resolved the issue by: - Set numpy < 2.0.0 to resolve numpy VersionConflict - Sync requirements and toml - Reorder ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? CI passed Closes: https://github.com/vllm-project/vllm-ascend/issues/473 Signed-off-by: Yikun Jiang <yikunkero@gmail.com> 2025-04-07 16:07:21 +08:00			`"pybind11",`
[Misc] version control by setuptools_scm (#21) make package version control by setuptools_scm to keep the same with vllm Signed-off-by: wangxiyuan <wangxiyuan1007@gmail.com> 2025-02-10 09:36:09 +08:00			`"pyyaml",`
			`"scipy",`
Set numpy < 2.0.0 to resolve numpy VersionConflict (#476) ### What this PR does / why we need it? vLLM bumps numpy version to 2.x: https://github.com/vllm-project/vllm/commit/8427f70493ed67bf26cb9e7fa98ac202b991c37d , this will cause a `pip._vendor.pkg_resources.ContextualVersionConflict: (numpy 2.2.4 (/usr/local/python3.10/lib/python3.10/site-packages), Requirement.parse('numpy==1.26.4'), {'vllm-ascend'})` failure when vllm ascend install. This PR resolved the issue by: - Set numpy < 2.0.0 to resolve numpy VersionConflict - Sync requirements and toml - Reorder ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? CI passed Closes: https://github.com/vllm-project/vllm-ascend/issues/473 Signed-off-by: Yikun Jiang <yikunkero@gmail.com> 2025-04-07 16:07:21 +08:00			`"setuptools>=64",`
			`"setuptools-scm>=8",`
[CI] enable custom ops build (#466) ### What this PR does / why we need it? This PR enable custom ops build by default. ### Does this PR introduce _any_ user-facing change? Yes, users now install vllm-ascend from source will trigger custom ops build step. ### How was this patch tested? By image build and e2e CI --------- Signed-off-by: wangxiyuan <wangxiyuan1007@gmail.com> 2025-04-12 10:24:53 +08:00			`"torch_npu",`
Set numpy < 2.0.0 to resolve numpy VersionConflict (#476) ### What this PR does / why we need it? vLLM bumps numpy version to 2.x: https://github.com/vllm-project/vllm/commit/8427f70493ed67bf26cb9e7fa98ac202b991c37d , this will cause a `pip._vendor.pkg_resources.ContextualVersionConflict: (numpy 2.2.4 (/usr/local/python3.10/lib/python3.10/site-packages), Requirement.parse('numpy==1.26.4'), {'vllm-ascend'})` failure when vllm ascend install. This PR resolved the issue by: - Set numpy < 2.0.0 to resolve numpy VersionConflict - Sync requirements and toml - Reorder ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? CI passed Closes: https://github.com/vllm-project/vllm-ascend/issues/473 Signed-off-by: Yikun Jiang <yikunkero@gmail.com> 2025-04-07 16:07:21 +08:00			`"torch >= 2.5.1",`
Set torchvision<0.21.0 to match torch/torch_npu version (#479) ### What this PR does / why we need it? Set torchvision<0.21.0 to match torch/torch_npu version to resolve `RuntimeError: operator torchvision::nms does not exist`. Closes: https://github.com/vllm-project/vllm-ascend/issues/477 ### Does this PR introduce _any_ user-facing change? No ### How was this patch tested? CI passed Signed-off-by: Yikun Jiang <yikunkero@gmail.com> 2025-04-08 09:15:42 +08:00			`"torchvision<0.21.0",`
[Misc] version control by setuptools_scm (#21) make package version control by setuptools_scm to keep the same with vllm Signed-off-by: wangxiyuan <wangxiyuan1007@gmail.com> 2025-02-10 09:36:09 +08:00			`]`
			`build-backend = "setuptools.build_meta"`