condabin

[jacobwilliams]

I think the envrunner was changed in 1.8.1 or 1.8.2? I'm trying 1.8.2 now and I see a line like this:

call "%~dp0..\condabin\conda.bat" activate blah

That ../condabin directory doesn't exist in the environment that I'm installing my package in, so this doesn't work. I think it is assuming you are installing in the base environment?

I was using 1.8.0 before, which worked fine. Should I update to a newer version? Or would that still be there?

[jacobwilliams]

Looks like it was done in this commit: 1f9d981b38ce6e3419ae57456e3981a7c7f180c2

[newville]

@jacobwilliams Thanks -- I think I don't see this, but I'll have to double-check which version of conda I was using when testing. The whole thing is sort of fragile and should be more robust. On top of that, conda has proved to be a bit of a moving target.

Do you know what version of Anaconda and conda you are using?

[jacobwilliams]

I'm using Miniconda (windows, the one with python 3.9).

[newville]

@jacobwilliams For me, there are both condabin\conda.bat and. Scripts\activate.bat which both appear to work to set the base environment. They both call condabin\_conda_acvitate. It is sort of confusing which of these is "preferred".

In a61697f9f763b2d945, I put a test in the envrunner.bat file for each of these options. If you get a chance to try this out, can you let me know if that work for you? If so, I'd be happy to tag/push that as 1.9.1.