Hi ucbevng,
That exactly confirms my suspicion.
At some point, the path to cadet-cli was added to your global PATH environment variable. Because of that, it appears when you run where cadet-cli. CADET-Process detects the executable built from source on the PATH and assumes that this is the default CADET installation you want to use.
This behaviour is intended and not a CADET issue. The PATH variable is controlled by the user, and any executable placed there will be detected automatically.
Also note that if you are not working inside an isolated environment (e.g., a conda environment or a Python venv), this can easily lead to the issue you are seeing. On Windows you effectively only have one global PATH, which means you can only have one CADET installation reliably available via cadet-cli at a time. If multiple CADET installations exist on your system, the one that appears first on the PATH will be used, which may not be the one you intended.
You now have three options.
Option 1: Remove CADET from the global PATH and update with desired version (not recommended)
You could remove the CADET entry from the global PATH and replace it with the installation you actually want to use.
On Windows this can be done via:
Start Menu → search for Environment Variables → Edit the system environment variables → Environment Variables → select Path → Edit.
There you can remove the CADET entry or add a different one pointing to another CADET installation. After changing the PATH, you need to open a new terminal for the changes to take effect.
However, this approach is usually not ideal if you work with multiple CADET builds.
Option 2: Add the correct CADET installation to the environment you are using
Instead of relying on the global PATH, you can add the CADET installation to the PATH inside the environment you are working in.
For a Conda environment
Activate your environment:
conda activate your_env
Temporarily extend the PATH:
set PATH=C:\path\to\cadet;%PATH%
If you want this to persist for that environment:
conda env config vars set PATH=C:\path\to\cadet;%PATH%
Then deactivate and activate the environment again.
For a Python venv
Activate the environment and edit the activation script:
<venv>\Scripts\activate.bat
Add a line such as:
set PATH=C:\path\to\cadet;%PATH%
This ensures that the correct CADET version is used whenever that environment is activated.
Option 3: Direct configuration (recommended in your case)
In your situation, explicitly setting the CADET installation path is likely the simplest solution:
Cadet(
install_path=r"C:\Users\VN62442\source\repos\SMB\SMB\vcadet\Lib\site-packages\cadet_core"
)
This bypasses automatic detection and directly tells CADET-Process which installation should be used.
You already confirmed that this works for you, right? Does this solve your problem?
Cheers,
Hannah
.