Avoid conda in base env getting shadowed by other conda executables in other envs
#5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jaimergp
force-pushed
the
condabin-first
branch
from
4c4a640 to
542de04
Compare
jaimergp
changed the title
$CONDA_ROOT/condabin is always first in PATHconda in base env getting shadowed by other conda executables in other envs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
condaexecutable atbasecan be shadowed by an environment that shipsconda#4 by putting$CONDA_ROOT/condabinalways firstCONDA_EXEand friends env var exports to not confuse other conda's lingering around.This required vendoring
conda.activateso this will enable some further cleanups with time. For now I removed the JSON formatting stuff and the deprecated methods that were going to be removed in 25.3 anyway.