Anaconda / Spyder4.1.1 - anaconda

I had to update my spyder to version 4.1.1 so I updated Spyder to that specific version.
After updating and rebooting the spyder in my anaconda navigator would not start
Then I opened anaconda promopt and typed the commander spyder --reset which resetted
Then it wouldnt restart without an enormous page long of error. I rebooted my computer again.
Now I can open Spyder 4.1.1. but my import matplotlib as plt command won't import the desired library.
I checked in my current enviroment whether the matplotlib was present (It was gone for some odd reason). so I tried installing that package using the navigator (Tab "Enviroments" and then looking for it with the fuzzy search )
When I hit install, I can see in the bottom of the navigator that it is "installing" but then I get an error message stating: Multiple Errors Encountered
When I press "Learn more" it directs me to another website
I am very lost at the moment, it shouldnt be that hard to update spyder to a newer version?
Would anybody be able to help me out?

A small update: I have fully removed my python/anaconda enviroment and reinstalled it from a blank state. This gave me the solution. An 4 hour-ish struggle has come to an end. I do am curious what steps I could have taken in this ordeal without not having to fully reinstall Anaconda.

Related

Anaconda Navigator: Installation of packages problem

I have problems installing packages in the Anaconda Navigator. When I install a single package, for example, the requests package (which was marked as updateable), the window “Update Packages / The following packages will be modified:” pops up, but no packages are listed. The list is blank and nothing happens. This also happens, when I try to update another package. The window stays blank and the only thing I can do is cancel the update process (close the window).
I also tried to update the whole Anaconda installation via conda update anaconda. This also seems not to work: “Solving environment” shows up for more than an hour. Even if I reboot my computer (it’s a Dell Latitude Notebook and I have Windows 10 Enterprise installed). I have only base environment.
What could be the problem and what would be an appropriate solution?

Uninstaling anaconda deleted entire file system- can i recover it?

I was trying to install tensorflow, but it said it was already installed in anaconda, and I haven't been using anaconda navigator at all. I had installed anaconda a while ago, but I deleted it a while ago so wasn't sure why it was still there, guess I didn't delete it correctly. So I uninstalled it, and my entire Documents was gone on my computer. My theory is that the whole time I was in the anaconda virtualenv and didn't realize, so when I uninstalled it and all of it's dependencies it deleted my whole file system. Does anyone know how I could recover it?
Please explain how to fix this as you would explain to a 6month old child.
I tried redownloading anaconda hoping it would come back but it didn't. I don't mind using anaconda from here on forward but mainly just want my files back.

Difference Between Opening Jupyter Notebooks on Anaconda or the Terminal

I'm pretty new at this so thanks for the patience. I was trying to import some libraries like matplotlib into a Jupiter Notebook file and I would get an error claiming that "there is not module named matplotlib". After having a difficult time installing it through the terminal (every time I used 'pip install matplotlib' the command would terminate due to some error), I tried opening the notebook file through the Anaconda navigator (opening the anaconda navigator, clicking on the Jupyter Notebook, which is slower and less convenient). However, importing actually worked with this method. It was the exact same file. The only variation was the way I opened Jupyter Notebook.
My question is why does this happen? What is going on that I don't know? It seems like an important piece of information to understanding how file systems work but I can't figure it out. Also, how can I fix this?

Anaconda not working after Catalina Installation (accessing Jupyter notebooks)

I recently upgraded to MacOS Catalina to take advantage of various new features/improvements. Soon after installation, I noticed that a question grey mark appeared over the Anaconda icon in my applications. Additionally, my Anaconda files have seemingly been migrated to the "Relocated Items" folder now on my desktop.
I am not sure exactly how to deal with this. I have tried clicking the Anaconda icon with the question mark to launch it, but this fails. I have also attempted locating my Jupyter notebooks in the relocated items file but have not been able to do so successfully.
My question is what do I need to do to fix this problem to restore normal functionality back? Do I need to reinstall Anaconda? Will this new installation have my old Jupyter notebooks?
From a little reading online I have found that Apple says that no files should be deleted; therefore, in theory, there should be no loss of data from the upgrade. I am just not sure how I can restore access to these Jupyter notebooks.
Not sure if anyone else has experienced a similar problem. Any help or general guidance would be greatly appreciated.
Thanks.
Answer: As I just found out, Anaconda rolled out a new update to address this issue. I went to their website here and just downloaded a fresh installation of the latest version of Anaconda. This worked great and completely fixed the issue. I can now access all of my pervious Jupyter notebooks.

Anaconda Spyder keeps crashing after a while

I am new and learning Python and its development tools, so please help me to resolve following issue.
I have googled the error over and over but I fail to find a solution to my exact error. I have tried uninstalling and re-installing twice with no success.
I am using Anaconda's Spyder IDE and whenever I leave my PC unattended for a bit and I return, I am presented with the following crash error:
The result is that Python becomes unresponsive and I am forced to restart.
Please note that everything else is working fine; it is merely this annoying crash.

Resources