Skip to main content
I compared my environment before activating sudo and after and found that the activate defines /conda/envs/sudo/lib in the LIBPATH but there is no /lib under /sudo ...?

Is this a known 'bug' in the conda setup for sudo?
I compared my environment before activating sudo and after and found that the activate defines /conda/envs/sudo/lib in the LIBPATH but there is no /lib under /sudo ...?

Is this a known 'bug' in the conda setup for sudo?
Hi Lionel,

It's not a bug it's how conda works, it adds LIBPATH, PATH when environment is activated.
You can even try on empty environment:
conda create -n empty -qy
conda activate empty
env | sort 

Thanks
I compared my environment before activating sudo and after and found that the activate defines /conda/envs/sudo/lib in the LIBPATH but there is no /lib under /sudo ...?

Is this a known 'bug' in the conda setup for sudo?
My issue isn't that it is in the LIBPATH but that it does not exist in the filesystem. ???
I compared my environment before activating sudo and after and found that the activate defines /conda/envs/sudo/lib in the LIBPATH but there is no /lib under /sudo ...?

Is this a known 'bug' in the conda setup for sudo?
The lib folder will be created after installing any package that has lib in its structure, for example, python, since sudo has no "lib" in the structure, it was not created
Terms & ConditionsAccessibility statement