I've lately noticed an increasing lag when I fire up the CMD window to run python.
Immediately after entering "python", I see the python version info, but instead of the command prompt (>>>) I just get a blinking cursor (not showing in screenshot). After what's now become a couple of minutes, the command prompt finally appears, and I can run python code as usual.
When this happens, the CPU on my little work laptop is clearly under heavy load, the fan goes way up.
I have basically the same setup on my home PC (still with the older Anaconda and python 3.7) and never had any problems like this.
I was running python 3.7 in Anaconda on Windows 10. I just do simple scripts, copy and paste the code in a terminal window. In my original version, I had the base env + one clone, both had this problem.
I tried updating conda and anaconda but nothing changed. I thought it might be some dependency conflicts (I had recently pip-installed a couple of heavy-ish packages into my clone env: pytessearct and openpyxl), so I finally uninstalled Anaconda and reinstalled the latest version (Anaconda3-2020.07-Windows-x86_64 with python 3.8) with the standard packages, and I still have the same problem.
One related clue: Anaconda Navigator was also hecka slow to load. I tried disabling SSL verification per this thread (Anaconda navigator VERY slow) but it had no effect on the time delay for the python command prompt. But with the fresh install, Navigator now loads normally.
In my new install, I did the same setup, base + clone, both with the standard Anaconda package set, no add-ons, I still have the same problem in both envs.
Related
I removed and started with a fresh new installation of Anaconda.
Just after installation I created a custom environment (cust_env)
Both the cust_env and the base environment have Python 3.9.
I then installed on both environments Spyder 5.1.
Now, the problem is the following:
If I run Spyder from the base environment, it seems to work and debug my code normally, while if I run it from the cust_env, when I enter in debug mode the console apparently does not answer anymore (the debug prompt does not appear and you must restart the kernel to have it back again).
I also tryed with different versions of Python (3.7.x and 3.8.x) and of Spyder (4.x, 3.x) and the behaviour looks identical.
I cannot understand what might be the difference which does not allow to use Spyder in an environment different to the base one.
I was able to delimit the problem and find a workaround.
The base problem is that, when you create a new environment of Anaconda, since it contains very few packages (Python and few more), when you afterwards install a new package, it is fully updated with all its dependancies.
In particular
conda install spyder
installs Spyder and all its dependancies at the very last available version.
On the opposite side, the base environment of Anaconda already contains plenty of packages and conda does it best to install the most updated version which is still compatible with the existing packages, but very often it is not the last one.
Now, it appears that Spyder uses QT to show the graphical interface and one of its dependancies qtconsole=5.2.2 has some bug which causes the problem.
When installing Spyder from the base environment, conda installs qtconsole=5.1.1 and the problem does not appear while, if installing from a fresh new environment, qtconsole=5.2.2 is installed and the problem shows up.
Therefore, is is sufficient to downgrade qtconsole
conda install qtconsole=5.1.1
to fix the problem.
I recently got a new M1 MacBook and have been trying to get my Python Dev environment setup. I’m new to conda (previously used virtualenv) and I’m wondering if there’s a way to use the Python 3.9.4 universal2 install. 3.9.2 is the highest version listed, and I can’t see how to distinguish it from the Intel/ARM installations, but running platform.machine() outputs x86_64, so it seems I have the Intel install by default. Any way to manage this?
Step 1: Come here
Scroll down to the line Anaconda 2019.03 for macOS Installer.
You need to know your Python version. To do this, write in the terminal
And select Command Line Installer
Step 2: installing via command line
After the installation is complete, go to the terminal.
If you have Python 3.7, then run:
bash ~ / Downloads / Anaconda3–2019.03-MacOSX-x86_64.sh
For Python 2.7:
bash ~ / Downloads / Anaconda2–2019.03-MacOSX-x86_64.sh
Attention: if you downloaded Anaconda not in the Downloads folder, then in the commands you need to change the path to the distribution kit.
Review the license agreement and press Enter. Finally, after a million Enter hits, type yes if you accept the license agreement.
(If you do not accept the agreement in time, then this clue will constantly catch your eye)
if you are satisfied with the installation path, then press Enter. You can change the location or abort the installation by pressing CTRL-C.
Then you will be asked: Do you wish the installer to initialize Anaconda3 by running conda init? Write yes, of course.
When the installation is complete, close a terminal window and open a new one - this will take effect your changes. Want to make sure everything works? Type conda list and see what happens. If everything works, you will see something like this:
If everything works, then congratulations! Now you can use Anaconda, Jupyter Notebooks, Spyder and other useful things.
Currently, I am watching an online course for python. That course is using Anaconda for the libraries etc.
Installing Anaconda on Windows 7 works perfectly fine. But I want to use all of the Stuff on Ubuntu since Linux works better for the stuff I want to develop.
Everything works fine from the point of downloading Anaconda for Linux, running it in the terminal and installing it.
The installations return Success "Thanks for installing Anaconda3!"
But from that point on nothing works. The installed folder with its files is there. But I cannot run the programm from the terminal, nor from a simple double-click on the symbol. Cause there is no symbol anywhere for it. Running it through the terminal by using the command "anaconda notebook", "Anaconda" etc. all don't work.
It acts like the programm isn't installed. Even tho it is. I reinstalled it several times. But it all doesn't work. I'm starting to get mad tbh...
Ubuntu runs over a virtual machine if that is important. VM Ware Workstation v14
I am currently using Spyder and have been for a long time, however I downloaded anaconda recently and started using Spyder for Python 3.5 which gives me several problems.
Whenever I run a script in the Python Console, I have to run it twice and then when I am finished running it and want to run a new I have to kill the current process and reload it.
I am currently using some scripts with threading, but that never used to be a problem before I upgraded, anyone have similar experiences and know how to fix it?
(Spyder developer here) We're aware of these problems in the Python console, but unfortunately we don't know how to fix them.
Please use the IPython console instead because the Python console is going to be removed in Spyder 3.2.
I observe some problems of users about Spyder Console.Effective example for solution;
via Anaconda prompt:
conda create -n spyder-env spyder=4
conda env list
conda activate speder-env
spyder
I had a working version of Anaconda 2.3 on my Windows 10 PC. (I use PowerShell as my preferred command line interface.)
After updating to Anaconda 2.4, any command using conda or anaconda resulted in the message failed to start process.
I tried and uninstalling, redownloading and reinstalling, and even tried reverting to 2.3. Nothing worked!
Starting to get desperate, I eventually found the solution: I used python to run the script conda-script.py, which is apparently what the command conda.exe runs when called:
python PATH_TO_ANACONDA\Anaconda3\Scripts\conda-script.py
(Here, I'm using PATH_TO_ANACONDA to represent the directory in which the Anaconda3 folder resides on my particular system.)
Thereafter, both conda and anaconda commands work perfectly, and continue to work. (e.g. No need to repeat the process every time I launch PowerShell.). But I have no idea why the problem occurred, or why that happened to be the solution.
If you know, please reply. If not, I just hope this solution saves others an hour or so of frustration.