In general, activating a conda environment _should_ override your PATH to include the environment's local, contained copy of both python and pip. As such, using pip install x in a conda environment will install those dependencies using your conda environment's python/pip, not your global python/pip.
On bash, you would test this like:
```sh
> conda activate env-name
> which python
$ # should be your local conda env path
> which pip
$ # should also be your local conda env, not global pip
```
If it _is_ using your global pip, that means somehow your PATH isn't being set properly. This is common with conda on windows, although I'm not certain why exactly.
The reason they are using pip inside of conda instead of conda may be because CUDA needs dependencies which are not found in conda's repositories, or simply due to personal preference.
On bash, you would test this like:
```sh
> conda activate env-name
> which python
$ # should be your local conda env path
> which pip
$ # should also be your local conda env, not global pip
```
If it _is_ using your global pip, that means somehow your PATH isn't being set properly. This is common with conda on windows, although I'm not certain why exactly.
The reason they are using pip inside of conda instead of conda may be because CUDA needs dependencies which are not found in conda's repositories, or simply due to personal preference.