Anaconda Navigator 不更新软件包
问题描述
我正在尝试通过 Anaconda Navigator 更新我的环境.但它无法更新某些软件包.如您所见,Apply 按钮处于非活动状态,并且有一条消息说Package is already installed",但该包仍在可更新页面中.此外,Spyder 告诉我在每次启动时更新 nbconvert.
I'm trying to update my environment through Anaconda Navigator. But it fails to update some packages. As you can see, the Apply button is inactive and there is a message saying "Package is already installed" but the package is still in Updatable page. Also, Spyder tells me to update nbconvert at each start.
我试过了:
- conda 更新 conda
- conda 更新 anaconda-navigator
- conda 更新导航器更新程序
- conda 更新 --all -y
但这些包仍然在可更新列表中.
But still these packages are in Updatable list.
这是 conda 信息输出:
This is the conda info output:
C:Usersuser>conda info
active environment : None
user config file : C:Usersuser.condarc
populated config files : C:Usersuser.condarc
conda version : 4.6.8
conda-build version : 3.17.8
python version : 3.6.8.final.0
base environment : C:UsersismetbAnaconda3 (writable)
channel URLs : https://repo.anaconda.com/pkgs/main/win-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/free/win-64
https://repo.anaconda.com/pkgs/free/noarch
https://repo.anaconda.com/pkgs/r/win-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/msys2/win-64
https://repo.anaconda.com/pkgs/msys2/noarch
package cache : C:UsersuserAnaconda3pkgs
C:Usersuser.condapkgs
C:UsersuserAppDataLocalcondacondapkgs
envs directories : C:UsersuserAnaconda3envs
C:Usersuser.condaenvs
C:UsersuserAppDataLocalcondacondaenvs
platform : win-64
user-agent : conda/4.6.8 requests/2.21.0 CPython/3.6.8 Windows/10 Windows/10.0.17134
administrator : False
netrc file : None
offline mode : False
我该如何解决这个问题?
How can I solve this?
解决方案
我发现可行的解决方案是 替代方法在 anaconda 网站上找到.
The solution I found to work is the alternative method found on the anaconda site.
在终端类型中:
conda deactivate
接着是:
conda update anaconda-navigator
其他解决方案更新了软件包,但没有更新 Anaconda Navigator 本身.在您的情况下,似乎问题可能没有首先停用.
Other solutions updated the packages but not Anaconda Navigator itself. In your case, it seems the issue might have been not deactivating first.
相关文章