spyder: Fresh installation of Anaconda with conda 4.7 doesn't allow to update Spyder

Description

What steps will reproduce the problem?

i don’t know ,i just download the ananconda from website and install

Traceback

  File "D:\Users\i-pengyunshan\AppData\Local\Continuum\anaconda3\lib\site-packages\spyder\plugins\__init__.py", line 515, in <lambda>
    toggled=lambda checked: self.toggle_view(checked),
  File "D:\Users\i-pengyunshan\AppData\Local\Continuum\anaconda3\lib\site-packages\spyder\plugins\ipythonconsole.py", line 771, in toggle_view
    self.create_new_client(give_focus=False)
  File "D:\Users\i-pengyunshan\AppData\Local\Continuum\anaconda3\lib\site-packages\spyder\plugins\ipythonconsole.py", line 1111, in create_new_client
    self.register_client(client)
  File "D:\Users\i-pengyunshan\AppData\Local\Continuum\anaconda3\lib\site-packages\spyder\plugins\ipythonconsole.py", line 1307, in register_client
    self.main.historylog.add_history(client.history_filename)
  File "D:\Users\i-pengyunshan\AppData\Local\Continuum\anaconda3\lib\site-packages\spyder\plugins\history.py", line 240, in add_history
    encoding.write(text, filename)
  File "D:\Users\i-pengyunshan\AppData\Local\Continuum\anaconda3\lib\site-packages\spyder\utils\encoding.py", line 233, in write
    with open(filename, mode) as textfile:
PermissionError: [Errno 13] Permission denied: 'C:\\Users\\i-pengyunshan\\.spyder-py3\\history.py'

Versions

  • Spyder version: 3.3.3
  • Python version: 3.7.3
  • Qt version: 5.9.6
  • PyQt5 version: 5.9.2
  • Operating System: Windows 10

Dependencies

pyflakes >=0.6.0  :  2.1.1 (OK)
pycodestyle >=2.3 :  2.5.0 (OK)
pygments >=2.0    :  2.3.1 (OK)
sphinx >=0.6.6    :  1.8.5 (OK)
rope >=0.9.4      :  0.12.0 (OK)
jedi >=0.9.0      :  0.13.3 (OK)
nbconvert >=4.0   :  5.4.1 (OK)
pandas >=0.13.1   :  0.24.2 (OK)
numpy >=1.7       :  1.16.2 (OK)
sympy >=0.7.3     :  1.3 (OK)
cython >=0.21     :  0.29.6 (OK)
qtconsole >=4.2.0 :  4.4.3 (OK)
IPython >=4.0     :  7.4.0 (OK)
matplotlib >=2.0.0:  3.0.3 (OK)
pylint >=0.25     :  2.3.1 (OK)

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Reactions: 3
  • Comments: 34 (25 by maintainers)

Most upvoted comments

I had similar issue, and it was happening because I had jupyter nb running on my machine. I closed it and was able to update packages using conda.

You updated the spyder-kernels requirement: https://github.com/AnacondaRecipes/spyder-feedstock/blame/master/recipe/meta.yaml#L48 but @dalthviz had at some point in the past explicitly specified spyder-kernels=0.4. Conda 4.7 tracks explicit requests much more that earlier versions. It uses the history to build up the specs, rather than using the state of the prefix to build up the specs. This is an optimization, but it also has the nice effect of allowing straightforward updates from earlier python packages that have shim packages, like enum34, to python versions that no longer need and indeed don’t have those shim packages. With the new behavior, the shims fall away, because they were never explicitly requested, and they lose their connection to any explicit request. The message tries to communicate that, but it’s probably a bit terse, especially if you aren’t familiar with that solver behavior change.

The following specifications were found to be in conflict with a past explicit spec that is not an explicit spec in this operation

In other words, “you asked for this specific thing earlier. I can’t fulfill your current request without breaking that past request. If you want to make this update, please tell me it’s ok to change your past request by adding a new explicit spec to your command that will allow this change”

You can either put in new bounds, or you can neuter it by just passing the package name.

@pengyunshan could you update conda to 4.7.10 and try updating Spyder again? Thanks 😃

Probably for Spyder 3.3.6 you will need to run something like conda install spyder=3.3.6 spyder-kernels=0.5 It’s WORD! I update the conda spyder,the history log return to normal! thx~

We think we fixed that one in 4.7.7. It’s on conda-canary if you want to try. The issue was a race condition caused by the repodata intake being parallelized. If the free channel content is loaded first, you get that error. If the main channel content is loaded first, you don’t.

Sure, if you have time and that’s not too complex.

@dalthviz, please update to conda 4.7.6 to see if that solves this problem.

This works fine for me on a totally vanilla python 3.7 env:

conda create -n py37env python=3.7 conda install -n py37env spyder=3.3.4

This is with stock conda - no free channel modification. Am I missing something? Are you trying to install into an existing env? Can you help me reproduce that initial env?

Ok, thanks @msarahan for the quick response!

@dalthviz, please do that and try again.

Probably related to https://github.com/conda/conda/issues/8844 please try to reenable the free channel and retry.

@dalthviz, please try with Anaconda3 on Linux, instead of using version 2.

This is interesting. @dalthviz, could you downgrade to conda 4.6 and try again? I think this could be a problem with the latest conda solver.

Also, could you reproduce this in a different Windows account by installing the latest Anaconda for that user and trying again?

Besides, please try this on Linux too to see if it’s not a Windows only issue. Thanks!

@dalthviz, let’s try to reproduce this error. Please update conda to its latest version (4.7.5) install the anaconda package in a new environment, then try to update Spyder with

conda install spyder=3.3.4

This seems to be a conflict between the latest anaconda package (which demands Spyder 3.3.3) and Spyder 3.3.4, which has a different requirement on spyder-kernels.