Unfortunately, it's hard to tell which state it's in. Many find Mamba, the drop-in replacement for Conda, to be more reliable (and definitely faster!). This happens, and especially happens when mixing channels ( defaults and conda-forge). The solver is reporting trouble solving when it really shouldn't be. E.g., ipykernel if you plan on using it as a Jupyter kernel.Ĭonda solver is bugging out. Include whatever other packages you need in there. In that case, you either need to track down the conflicting constraints and try to manually loosen them (not recommended for Anaconda base), or you need to make a new environment: conda create -n pygmo_env -c conda-forge pygmo The previous package constraints you have in the environment are incompatible with installing pygmo. And I tried this hint as wellĬonda solver is correct. I also tried the installation commands from PyPI. I also checked this command but that is essentially the same thing.
I followed the official installation guidelines and set the additional channel and its priority. Note that strict channel priority may have removed packages required for satisfiability. Here is a representative piece of output: Package selectors2 conflicts for: Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.Ĭollecting package metadata (repodata.json): doneįound conflicts! Looking for incompatible packages.Īfter few hours, the Terminal returns a long report of conflicts and stops there. Solving environment: failed with initial frozen solve.
MAC OS 10.15 ANACONDA FAIL INSTALL
Here is the start: $ conda install -c conda-forge pygmoĬollecting package metadata (current_repodata.json): done How can I solve the conflict so that I can run PyGMO?
MAC OS 10.15 ANACONDA FAIL MAC OS X
I am attempting to install PyGMO on Mac OS X 11.2.2 (with Anaconda which I reinstalled so the Anaconda Navigator is now upgraded to 2.0.1.)Īfter the installation starts, it collects package metadata and reports it found package conflicts.
0 kommentar(er)
