Closed langmm closed 3 years ago
Update: I've also been able to trigger this behavior by calling conda deactivate
Looks like at https://github.com/conda-forge/msmpi-feedstock/blob/58b78e6ac8024e1f34722c5de0a9fe0bf6bd2601/recipe/deactivate.bat#L6 there's a brace instead of parenthesis.
Good catch! I will create a PR w/ the change (unless there is a reason to hold off or if you would prefer to make it?)
Issue:
After installing msmpi from an environment or updating a conda environment that contains msmpi, conda can no longer deactivate the environment or activate another environment (conda info continues to display the same information for the environment containing msmpi and no longer displays the environment name in the prompt). Is this expected behavior?
The problem can be reproduced via the following:
When called from a batch script (
call conda update --all
) a process error code is returned (caught by calling the script from a Python subprocess). I discovered this problem when trying to update a conda environment in one of my CI setup scripts (I can provide this build if it is helpful, but it is part of a much larger build).Environment (
conda list
):Details about
conda
and system (conda info
):Any help with this is much appreciated as my current work around is prone to obscuring problems in the future (do all updates before installing mpi4py, install mpi4py w/ the local conda build for the target package, and ignore the error).