vim-conda is not compatible with the latest conda env activation mechanism

Starting from Conda 4.4, the recommended way of activating conda env has been changed.

Now when I execute CondaChangeEnv command with the latest setup (setting . /opt/conda/etc/profile.d/conda.sh in .bashrc). The vim command complains as follows:

~/.conda/envs/vim_test/lib/python3.6/subprocess.py in check_output(timeout, *popenargs, **kwargs)
    334 
    335     return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
--> 336                **kwargs).stdout
    337 
    338 

~/.conda/envs/vim_test/lib/python3.6/subprocess.py in run(input, timeout, check, *popenargs, **kwargs)
    416         if check and retcode:
    417             raise CalledProcessError(retcode, process.args,
--> 418                                      output=stdout, stderr=stderr)
    419     return CompletedProcess(process.args, retcode, stdout, stderr)
    420 

CalledProcessError: Command 'conda info --json' returned non-zero exit status 127.

Changing back to the old export PATH=... solves the above issue. But would it be possible to be compatible with latest conda? Thank you!

[cjrh]

@Nikasa1889 If you submit a PR that fixes this problem, I will merge it and make you a contributor to this repo.

[cjrh]

If you submit a pull request to fix this I will likely merge it. I don’t use Conda anymore, so we should also check with: @jfishe @hstarmans @ryanfreckleton