Apply feedback

Author: vzhurba01

cuda_bindings/README.md

@@ -19,9 +19,9 @@ Differences between these options are described in [Installation](https://nvidia
 CUDA Python is supported on all platforms that CUDA is supported. Specific dependencies are as follows:
 
 * Driver: Linux (450.80.02 or later) Windows (456.38 or later)
-* CUDA Toolkit 12.0 to 12.6
+* CUDA Toolkit 12.x
 
-Only the NVRTC redistributable component is required from the CUDA Toolkit. [CUDA Toolkit Documentation](https://docs.nvidia.com/cuda/index.html) Installation Guides can be used for guidance. Note that the NVRTC component in the Toolkit can be obtained via PYPI, Conda or Local Installer.
+Only the NVRTC and nvJitLink redistributable components are required from the CUDA Toolkit, which can be obtained via PyPI, Conda, or local installers (as described in the CUDA Toolkit [Windows](https://docs.nvidia.com/cuda/cuda-installation-guide-microsoft-windows/index.html) and [Linux](https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html) Installation Guides).
 
 ### Supported Python Versions
 
@@ -73,18 +73,18 @@ Multiple testing options are available:
 Responsible for validating different binding usage patterns. Unit test `test_kernelParams.py` is particularly special since it demonstrates various approaches in setting up kernel launch parameters.
 
 To run these tests:
-* `python -m pytest tests/` against local builds
+* `python -m pytest tests/` against editable installations
 * `pytest tests/` against installed packages
 
 ### Cython Unit Tests
 
-Cython tests are located in `tests/cython` and need to be built. These builds have the same CUDA Toolkit header requirements as [Installing from Source](https://nvidia.github.io/cuda-python/cuda-bindings/latest/install.html#requirements) where the major.minor version must match `cuda-python`. To build them:
+Cython tests are located in `tests/cython` and need to be built. These builds have the same CUDA Toolkit header requirements as [Installing from Source](https://nvidia.github.io/cuda-python/cuda-bindings/latest/install.html#requirements) where the major.minor version must match `cuda.bindings`. To build them:
 
 1. Setup environment variable `CUDA_HOME` with the path to the CUDA Toolkit installation.
 2. Run `build_tests` script located in `test/cython` appropriate to your platform. This will both cythonize the tests and build them.
 
 To run these tests:
-* `python -m pytest tests/cython/` against local builds
+* `python -m pytest tests/cython/` against editable installations
 * `pytest tests/cython/` against installed packages
 
 ### Samples
@@ -102,13 +102,13 @@ In addition, extra examples are included:
   wrappers of the driver API.
 
 To run these samples:
-* `python -m pytest tests/cython/` against local builds
+* `python -m pytest tests/cython/` against editable installations
 * `pytest tests/cython/` against installed packages
 
 ### Benchmark (WIP)
 
 Benchmarks were used for performance analysis during initial release of CUDA Python. Today they need to be updated the 12.x toolkit and are work in progress.
 
 The intended way to run these benchmarks was:
-* `python -m pytest --benchmark-only benchmark/` against local builds
+* `python -m pytest --benchmark-only benchmark/` against editable installations
 * `pytest --benchmark-only benchmark/` against installed packages

cuda_bindings/docs/source/install.md

@@ -2,12 +2,13 @@
 
 ## Runtime Requirements
 
-`cuda-python` supports the same platforms as CUDA. Runtime dependencies are:
+`cuda.bindings` supports the same platforms as CUDA. Runtime dependencies are:
 
 * Driver: Linux (450.80.02 or later) Windows (456.38 or later)
-* CUDA Toolkit 12.0 to 12.6
+* CUDA Toolkit 12.x
 
-```{note} Only the NVRTC redistributable component is required from the CUDA Toolkit. [CUDA Toolkit Documentation](https://docs.nvidia.com/cuda/index.html) Installation Guides can be used for guidance. Note that the NVRTC component in the Toolkit can be obtained via PYPI, Conda or local installers.
+```{note}
+Only the NVRTC and nvJitLink redistributable components are required from the CUDA Toolkit, which can be obtained via PyPI, Conda, or local installers (as described in the CUDA Toolkit [Windows](https://docs.nvidia.com/cuda/cuda-installation-guide-microsoft-windows/index.html) and [Linux](https://docs.nvidia.com/cuda/cuda-installation-guide-linux/index.html) Installation Guides).
 ```
 
 ## Installing from PyPI
@@ -19,48 +20,33 @@ $ pip install cuda-python
 ## Installing from Conda
 
 ```console
-$ conda install -c nvidia cuda-python
+$ conda install -c conda-forge cuda-python
 ```
 
-Conda packages have dependencies to CUDA Toolkit components:
-
-* cuda-cudart (Provides CUDA headers to enable writing NVRTC kernels with CUDA types)
-* cuda-nvrtc (Provides NVRTC shared library)
-
 ## Installing from Source
 
 ### Requirements
 
 * CUDA Toolkit headers[^1]
-* [requirements.txt](https://github.com/NVIDIA/cuda-python/blob/main/cuda_bindings/requirements.txt)
 
-[^1]: User projects that `cimport` CUDA symbols in Cython must also use CUDA Toolkit (CTK) types as provided by the `cuda-python` major.minor version. This results in CTK headers becoming a transitive dependency of downstream projects through CUDA Python.
+[^1]: User projects that `cimport` CUDA symbols in Cython must also use CUDA Toolkit (CTK) types as provided by the `cuda.bindings` major.minor version. This results in CTK headers becoming a transitive dependency of downstream projects through CUDA Python.
 
-Source builds require that the provided CUDA headers are of the same major.minor version as the `cuda-python` bindings you're trying to build. Despite of this requirement, note that the minor version compatibility is still maintained. Use the `CUDA_HOME` (or `CUDA_PATH`) environment variable to specify the location of your headers. For example, if your headers are located in `/usr/local/cuda/include`, then you should set `CUDA_HOME` with:
+Source builds require that the provided CUDA headers are of the same major.minor version as the `cuda.bindings` you're trying to build. Despite this requirement, note that the minor version compatibility is still maintained. Use the `CUDA_HOME` (or `CUDA_PATH`) environment variable to specify the location of your headers. For example, if your headers are located in `/usr/local/cuda/include`, then you should set `CUDA_HOME` with:
 
 ```console
 $ export CUDA_HOME=/usr/local/cuda
 ```
 
-```{note} Only `cydriver`, `cyruntime` and `cynvrtc` are impacted by the header requirement.
-```
-
-### In-place
-
-To compile the extension in-place, run:
-
-```console
-$ python setup.py build_ext --inplace
+```{note}
+Only `cydriver`, `cyruntime` and `cynvrtc` are impacted by the header requirement.
 ```
 
-To compile for debugging the extension modules with gdb, pass the `--debug` argument to setup.py.
-
-### Develop
+### Editable Install
 
 You can use
 
 ```console
-$ pip install -e .
+$ pip install -v -e .
 ```
 
 to install the module as editable in your current Python environment (e.g. for testing of porting other libraries to use the binding).

cuda_core/README.md

@@ -39,5 +39,5 @@ for more details, including how to sign your commits.
 ## Testing
 
 To run these tests:
-* `python -m pytest tests/` against local builds
+* `python -m pytest tests/` against editable installations
 * `pytest tests/` against installed packages