Closed isaacovercast closed 1 year ago
I have been having this problem with a number of packages and conda. One switch around form your suggested is I would recommend installing mamba within the conda environments. Having it not within some environments caused even wackier errors to be thrown (not for ipyrad mind you).
Just a suggestion :).
The conda-libmamba-solver is now packaged by default with conda, so it's much easier to switch the default solver on conda install you just pass the additional flag: --solver=libmamba
The conda resolver is very very very slow on intel macs these days for some reason that I can't figure out. The easiest thing to do is work around it by using the
mamba
package, which has a reimplemented solver that actually works:This is not a great solution, because optimally conda ipyrad install would work natively, but this is a reasonable workaround.