verticalzuloo.blogg.se - Conda upgrade package

CONDA UPGRADE PACKAGE HOW TO
CONDA UPGRADE PACKAGE INSTALL

We'll try to both improve the docs and make the behavior more defined and predictable. This may be true on initial install, but does not seem to hold for updates.

CONDA UPGRADE PACKAGE INSTALL

Instead use conda update -all to keep packages up to date, and use conda install anaconda= to explicitly update to a new anaconda release.Īs a side note, the notion that the custom anaconda package is lower in version ordering than any actual release is bizarre. So in summary, there currently seems little use for conda update anaconda.

NONSENSE: With Anaconda 2019.07’s newer Anaconda metapackage, conda update -all should update you to that version, along with all of that version’s pins.

FALSE: If you have the Anaconda metapackage version 2019.03, conda update -all should not update any dependencies that are in that metapackage because that metapackage constrains the solution.

TRUE: conda update -all may not be able to make everything the latest versions because you may have conflicting constraints in your environment.

TRUE: conda update -all updates all packages in the current environment to the latest version.

FALSE: conda update anaconda grabs the latest release of the Anaconda metapackage.

The advice in Updating from older versions is misleading. Instead, as is mentioned in ContinuumIO/anaconda-issues#9328, it will update all of anaconda's dependencies to their latest versions.

I think the catch is that conda update anaconda does not, as if often advertised, update to the latest anaconda release along with its version constrained dependencies. ) and playing around a lot with combinations of those commands my current conclusion still is that the safest (and probably fastest) way to get a working, up-to-date Anaconda environment is to completely uninstall Anaconda, and then reinstalling everything.Īs of now, I can confirm your observation that (with conda version 4.7.12) starting in an env with anconda=2019.07 that conda update anaconda does want to update to custom anaconda.

CONDA UPGRADE PACKAGE HOW TO

So, after reading quite a bit about the "correct" procedure of how to update anaconda (conda update conda followed by conda update anaconda, or conda update -all, or conda install anaconda. And when I do that, and then run conda update anaconda, I get the "dreaded" message about an "inconsistent environment" (for packages anaconda and numba). conda install anaconda=2019.07), strange things happen - when I do that on my freshly installed 2019.07, it proposes to update conda to 4.7.12. custom-p圓7_1 does not really strike me as an official "stable release" tag, right?Ĭuriously enough, even when specifying specific version to conda install (e.g. For example, with a just now newly installed version of 2019.07, conda update anaconda proposes to update several packages, and would "downgrade" anaconda (2019.07-p圓7_0 -> custom-p圓7_1). This is however not at all what happens.Ĭonda update anaconda does NOT try to install the latest "stable release", at least in none of the many times I have tried it. here: ) seems to be at least misleading I read it that conda update anaconda should update to the latest "stable release" of Anaconda. This information (and the information I found everywhere else, e.g.

A few instances of over specified dependencies in the Anaconda metadata have been fixed.Ĭonda update anaconda updates Anaconda, the single metapackage with explicitly pinned versions of several hundred individual packages.

For conda update -all, it shouldn't take more than a minute at the absolute worst on a reasonably fast machine. It should generally finish, though, unless you run out of memory, or are too impatient. Not many changes have been made in the past six months there (one memory leak in Python 2 has been fixed recently).

The algorithm can still be a little slow.

It no longer hangs or bails with no hint.

The unsatisfiable package specification hint generation is now very fast, even for a large number of packages.

Since conda already tries to make everything as up-to-date as possible, this results in far fewer unsatisfiability issues, which were usually caused because one package's dependency specifications required another to be downgraded. That is, it can downgrade a package, if it leads to the overall satisfiability of packages.

conda update -all no longer requires that each package that is installed be updated only.

As noted, conda update anaconda and conda update -all are mutually exclusive ways of keeping things up-to-date. Since anaconda almost always prevents updates, it makes little sense to include it.

conda update -all completely ignores the anaconda metapackage.

A few changes have been made in the past few months: