Description
Basically I'm after a way to know what would change in a user's environment when they run conda activate myenv (and I'm personally fine if this doesn't include custom shell scripts from the user). The reason for this is that on VS Code it would be easier to run commands in an activated environment, but conda run has buffered I/O issues and activating environments upon terminal creation creates a race condition between the activation and the command to be executed (and usually the command beats the activation). So we are trying to think of ways to solve this problem and one idea was to reconstruct the environment variables on behalf of the user if we knew what needed changing.
I would totally take documentation on this as well, but my guess is you wouldn't want to hard-code this information.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status