Fresh installation of Anaconda with conda 4.7 doesn't allow to update Spyder
See original GitHub issueDescription
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)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:34 (25 by maintainers)
Top Results From Across the Web
Anaconda won't update spyder 4 - Stack Overflow
Open the Anaconda Navigator · Go to the spyder tile · Click on the gear icon on the spyder tile · Choose from...
Read more >Release notes — conda 22.11.1.post14+4f2f30268 ...
Notices will be intermittently shown after running, install , create , update , env create or env update . New notices will only...
Read more >Anaconda prompts me to create new environment in order to ...
I have encountered a problem while clicking install spyder in anaconda ... all the packages through command prompt using conda update --all.
Read more >How do you update Spyder through Anaconda? - Quora
You can use the command line program conda as follows: [code]conda update spyder [/code]Alternately, if you have installed Anaconda Navigator, ...
Read more >Installation Guide — Spyder 5 documentation
If Spyder does not start via this method or you prefer to use the command line, open Anaconda Prompt (Windows) or your terminal...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

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.
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.