ANACONDA 3 UPDATE PACKAGES INSTALL
ANACONDA 3 UPDATE PACKAGES UPGRADE
ANACONDA 3 UPDATE PACKAGES SERIES

Executing conda update -all inside such an environment will update the packages inside this environment. The command run in the base environment will update the packages in this, but usually you should work with virtual environments ( conda create -n myenv and then conda activate myenv). But that is only to hack your way around issues, definitely not the normal-user case!ġ If you actually want to update the packages of your installation, which you usually don't. Or break the compatibility of the packages (which you usually don't want!), which is only possible by explicitly invoking an ignore-dependencies and force-command.

ANACONDA 3 UPDATE PACKAGES UPGRADE

So you still cannot upgrade them all by doing the upgrades separately the dependencies are just not satisfiable so earlier or later, an upgrade will downgrade an already upgraded package again. ( this is a pedagogical example, of course, but it's the same in reality, usually just with more complicated dependencies and sub-dependencies) So upgrading Y > 5.0 implies downgrading X to < 2.0 and vice versa. This way conda does also search in this places for available packages.Ĭonsidering your update: You can upgrade them each separately, but doing so will not only include an upgrade but also a downgrade of another package as well. It's rather a hack.Ī safe way you can try is to add conda-forge as a channel when upgrading (add -c conda-forge as a flag) or any other channel you find that contains your package if you really need this new version.

If you do that, do it as a last resort and after all packages have been installed with conda.

ANACONDA 3 UPDATE PACKAGES INSTALL

But be aware that pip also installs packages if dependency conflicts exist and that it usually breaks your conda environment in the sense that you cannot reliably install with conda anymore. It is possible to install with pip, since more packages are available in pip. To add: maybe it could work but a newer version of X working with Y > 5.0 is not available in conda. A way to invoke it without installing mamba is via the -solver=libmamba flag (requires conda-libmamba-solver), as pointed out by matteo in the comments. Update 1: since a while, mamba has proven to be an extremely powerful drop-in replacement for conda in terms of dependency resolution and (IMH experience) finds solutions to problems where conda fails.

That's why you 'cannot' upgrade them all. Conda usually warns very explicitly if they occur. Dependency conflictsīut it is possible that there are dependency conflicts (which prevent a further upgrade).

ANACONDA 3 UPDATE PACKAGES SERIES

Conda always tries to upgrade the packages to the newest version in the series (say Python 2.x or 3.x). TL DR: dependency conflicts: Updating one requires (by its requirements) to downgrade another

Anaconda 3 update packages