Open leofang opened 5 months ago
It doesn't matter if a user installs with cuda-version=11 or 12. This is because we built cuquantum-python in conda’s CUDA 11 pipeline just for convenience: https://github.com/conda-forge/cuquantum-feedstock/blob/f170c6b5bcdfeb067ab7adb3cf70af6711c4a0fc/recipe/meta.yaml#L225-L231 The -cuXX suffix is part of the wheel-build pipeline (dynamically added at build time): https://github.com/NVIDIA/cuQuantum/blob/788c04862241c52a5435982e6c25b30b6e3e9324/python/setup.py#L130-L131
cuda-version=11
12
cuquantum-python
-cuXX
This is NOT a bug, just that the mechanisms of conda and pip for recording the package name are different. But, it would not hurt if we could investigate better ways to ensure alignment on conda/pip.
It doesn't matter if a user installs with
cuda-version=11or12. This is because we builtcuquantum-pythonin conda’s CUDA 11 pipeline just for convenience: https://github.com/conda-forge/cuquantum-feedstock/blob/f170c6b5bcdfeb067ab7adb3cf70af6711c4a0fc/recipe/meta.yaml#L225-L231 The-cuXXsuffix is part of the wheel-build pipeline (dynamically added at build time): https://github.com/NVIDIA/cuQuantum/blob/788c04862241c52a5435982e6c25b30b6e3e9324/python/setup.py#L130-L131This is NOT a bug, just that the mechanisms of conda and pip for recording the package name are different. But, it would not hurt if we could investigate better ways to ensure alignment on conda/pip.