( 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. 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. 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). 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 it's requirements) to downgrade another
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |