Problem
cuda.pathfinder.SUPPORTED_BINARY_UTILITIES currently includes the legacy GUI names nsight-sys and nsight-compute, but omits the executable names used by supported Nsight releases: nsys-ui and ncu-ui.
Because find_nvidia_binary_utility() treats the requested name literally (and appends .exe on Windows), calls using the legacy names return None on a current standalone Nsight installation even though the corresponding GUI is installed.
The CLI entries nsys and ncu are correct and should remain unchanged.
Evidence
These legacy names predate the CUDA Toolkit majors currently covered by cuda.pathfinder's “two most recent major versions” support policy.
Proposed change
- Replace
nsight-sys with nsys-ui and nsight-compute with ncu-ui in the supported binary descriptors.
- Preserve
nsys and ncu as the CLI utility names.
- Add standalone Windows discovery through the existing Nsight registry roots:
- Nsight Systems: locate
nsys-ui.exe under the host directory (for example, host-windows-x64).
- Nsight Compute: locate the root shortcut and/or the actual executable under
host/windows-desktop-*/ncu-ui.exe.
- Add tests for wheel/Conda layouts and standalone Windows layouts.
If removing names from the public supported tuple is considered too disruptive, a compatibility alternative is to retain the old inputs temporarily as deprecated aliases that resolve to the current UI executable, while documenting that the returned basename differs.
Expected behavior
find_nvidia_binary_utility("nsys-ui") # absolute path to nsys-ui[.exe]
find_nvidia_binary_utility("ncu-ui") # absolute path to ncu-ui[.exe]
find_nvidia_binary_utility("nsys") # unchanged
find_nvidia_binary_utility("ncu") # unchanged
Problem
cuda.pathfinder.SUPPORTED_BINARY_UTILITIEScurrently includes the legacy GUI namesnsight-sysandnsight-compute, but omits the executable names used by supported Nsight releases:nsys-uiandncu-ui.Because
find_nvidia_binary_utility()treats the requested name literally (and appends.exeon Windows), calls using the legacy names returnNoneon a current standalone Nsight installation even though the corresponding GUI is installed.The CLI entries
nsysandncuare correct and should remain unchanged.Evidence
https://github.com/NVIDIA/cuda-python/blob/main/cuda_pathfinder/cuda/pathfinder/_binaries/supported_nvidia_binaries.py
https://github.com/NVIDIA/cuda-python/blob/main/cuda_pathfinder/cuda/pathfinder/_binaries/find_nvidia_binary_utility.py
nsys-ui:https://docs.nvidia.com/nsight-systems/InstallationGuide/index.html#launching-the-gui
ncu-ui:https://docs.nvidia.com/nsight-compute/NsightCompute/index.html#quickstart
nsight-sys.exewas Nsight Systems 2020.3.4.32, bundled with CUDA Toolkit 11.1:https://developer.download.nvidia.com/compute/cuda/repos/windows/x86_64/version_11.1.0.json
These legacy names predate the CUDA Toolkit majors currently covered by cuda.pathfinder's “two most recent major versions” support policy.
Proposed change
nsight-syswithnsys-uiandnsight-computewithncu-uiin the supported binary descriptors.nsysandncuas the CLI utility names.nsys-ui.exeunder the host directory (for example,host-windows-x64).host/windows-desktop-*/ncu-ui.exe.If removing names from the public supported tuple is considered too disruptive, a compatibility alternative is to retain the old inputs temporarily as deprecated aliases that resolve to the current UI executable, while documenting that the returned basename differs.
Expected behavior