I'm currently using the Anaconda package with Python 2.7.9-1
Yesterday I upgraded the Spyder-app via the Anaconda Launcher and all of my scripts now crash. (Some bugs are already reported in the issues page https://github.com/spyder-ide/spyder/issues).
How can I downgrade to the previous Spyder version meanwhile those bugs are fixed?
You can install a specific version of spyder with conda. For instance, to install 2.3.5.2, run
conda install spyder-app=2.3.5.2
in the terminal.
In Anaconda Navigator, on Spyder tab, you have a settings symbol on top right corner. Press that and select 'Install specific version' option
Thanks for the answers.
What worked in the end was the following (I have windows 7 and the Anaconda Package):
1) In the anaconda prompt, type:
conda list -r
this is going to give you a list of all the packages updates you've done in the past.
2) Check the number of the update where you had the previous version of spyder (for example in my case was 2015-06-25 10:43:34 rev 4) and type:
conda install --revision=4
It would ask you if you want to downgrade, etc and thats it!
Now all scripts run again.
The previous answers didn't work for me, but going here: (https://docs.spyder-ide.org/installation.html). I found the following command works.
conda install -c conda-forge/label/beta spyder=4.1.3
or
conda install spyder=4.1.3*
Note: I had to do this today (7/17/20) where the most recent version is spyder=4.1.4 and I'm getting the following error in the console: "QSocketNotifier: Multiple socket notifiers for same socket 2068 and type Read"
As it is hosted on GitHub, you can find the desired version from the commit history and download that version easily.
First browse the commits:
https://github.com/spyder-ide/spyder/commits/master
After you find the version that doesn't break things. Then you can easily download and install it.
As mentioned before there is an option in the GUI now to select the preferred version.
But before that make sure to run conda update conda. At least in my case that helped.
Related
I am using spyder in anaconda to run my python program (added the figure below to show my version ) .
When I type input() command in editor window, an error pops up .
(above)I have attached the screenshots of the same.
If I retain first part alone, there is no error.
Can someone help me as to why this error pops up.
I reinstalled the anan conda several times, thinking it was an installation error
I think its a bug in anaconda-spyder which a lot of users have reported. I suggest one of the two appraoches :
Install 'non-anaconda' distribution of python and do pip install spyder.
Or check if your anaconda version is 5.1.5, if yes then check this - link or downgrade spyder or search other relevant links.
I'm trying Anaconda/Spyder after using the standard python installation/IDLE for several years. The console (and variable explorer) becomes progressively slower during each work session, with every script and interactive command that I run. Eventually it takes minutes to get a response to simple commands like print, and then it stops responding completely and I shut it down. It's pretty disruptive to my work.
Mac OSX 10.13.6
conda version : 4.5.11
conda-build version : 3.15.1
python version : 3.7.0.final.0
qt 5.9.6
spyder 3.3.1
ipython 7.1.1
I do use matplotlib frequently. Whenever possible I use plt.ioff() at the beginning of a script and/or plt.close('all') at the end. Turning off matplotlib support completely in preferences doesn't help and it's not a permanent fix anyway. Python is not using anywhere near all my CPU or RAM.
As far as I've found out, the problem seems to be with the latest major release of the ipython kernel. Pinning the version of ipykernel to 4.10.0 solved it for me. To do so, add a line containing ipykernel 4.* to the file ~/anaconda3/conda-meta/pinned. Create the file if it does not exist yet. Then conda update ipykernel which will actually downgrade to 4.10.0. Worked for me!
you don't need to downgrade the entire spyder.
For me it worked with downgrading these two:
conda install ipython=6.4.0
conda install ipykernel=4.10.0
So this is not a totally satisfying solution but it seems to be a reasonable temporary fix. If you downgrade your spyder version to 3.1.X you will be able to use the python console rather than the Ipython console, and this seems to work for me. To do this just run:
conda install spyder=3.1
in the terminal while your environment of choice is active. This is not ideal, because the developers removed the python console for a specific reason as mentioned in this question, How to add python console in spyder.
Additionally downgrading this much may have unforeseen effects on other packages your code uses and may cause other issues but so far this is the only solution I was able to come up with.
#Sjoerd Thanks for your answer, this is what worked for me. To be still clearer, here's what I did in terminal on Anaconda 3 on High Sierra:
echo "ipykernel 4.10.0" >> ~/anaconda3/conda-meta/pinned
conda update anaconda
When I tried to update only ipykernel, I would have dependencies errors. By updating anaconda, everything is now up to date but ipykernel which is effectively at version 4.10.0. I didn't experience any hang since then.
#JJR4's answer didn't work for me (seems to work for others). Another workaround is to type %connect_info magic command into the IPython Spyder console which will display the JSON info to connect another console to the kernel.
The output of the magic command explains how to connect, but basically there are three options.
Paste the above JSON into a file, and connect with:
$> jupyter <app> --existing <file>
or, if you are local, you can connect with just:
$> jupyter <app> --existing <kernel>.json
or even just:
$> jupyter <app> --existing
if this is the most recent Jupyter kernel you have started.
I typically use qtconsole as the app. Once you enter your chosen connection method into the command line, a new console will open that is connected to the same kernel as the console in Spyder. For some reason, the new console does not lag even if the Spyder console does.
Enter everything in the new console, even runfile()
Hope this helps!
UPDATE:
Downgrading to ipykernel version 4.10 seems to solve the issue for me. Thanks to Carlos Cordoba - see GitHub conversation in link below.
When I run:
import pyaudio
pa = pyaudio.PyAudio()
pa.get_default_output_device_info()
I get:
IOError: No Default Output Device Available
When I say:
pa.get_device_count()
It returns 0L.
And of course if I list devices
for i in range(0, device_count):
print("Name: " + pa.get_device_info_by_index(i)["name"])
print("Index: " + pa.get_device_info_by_index(i)["index"])
print("\n")
It will not print anything.
I'm running Ubuntu 16.04 and have set my default sink by going:
pacmd list-sinks
pacmd set-default-sink 0
I have the latest versions of PulseAudio, ALSA, and PortAudio. Any suggestions?
Update: I also can't view any sound devices on Audacity, despite the fact that they appear under System Settings>Sound. In Audacity I get the error:
Error while opening sound device. Please check the recording device
settings and the project sample rate.
I think that this is almost certainly a PortAudio issue since the settings page looks like:
Its likely a broken file that needs replacement.
Search for "/usr/./libstdc++.so.6" where pip installed it.
Search for "/usr/lib/x86_64-linux-gnu/libstdc++.so.6" and copy to location at (1). This should fix it.
If you have Anaconda version 3 - 4.3.0 or 4.4.0 or earlier installed then check at "anaconda3/lib/libstdc++.so.6" and replance with (2).
Alternatively A) rename the file and place the file from (2) where you renamed the old libstdc++.so.6 file or B) upgrade to Anaconda to 5.0.1 version and run conda update --all. And if you do "B" don't forget to remove the eggs or whls manually first to be sure there is no chance installing old software from there again.
This should fix it for you.
Enjoy ;-)
It looks like you're missing the package portaudio19-dev. Use the following command to install that package using the terminal:
sudo apt-get install portaudio19-dev
Install with apt-get; and run with python2. Or install with conda and run with python3.
I have windows 8.1 and tried installing: python-3.5.0rc3-amd64
I tried running as admin to no avail.
Here is the log of the failed install: http://pastebin.com/Y465P6zi.
Manually install the Universal C Runtime update from Microsoft:
https://support.microsoft.com/en-us/kb/2999226
and then re-attempt installation of Python 3.5.
I too had the same issue. Try installing Python 3.4.3. It worked for me.
You may try some older version. I had similar issues and I tried a lot to update but not succeed. Then I tried for python-3.4.3. It's works fine for me. There are not much different between 3.4.3 and 3.5.0.
Please update the window version from windows update(if you have blocked auto windows update).
This problem have nothing to do with product key.
Installing older version might help but, won't solve the purpose of installing the 3.5.X version
I had this problem because I was trying to install Python on a computer that had its Windows Updates downloaded, yet not yet installed and configured.
Solution: reboot your computer so that all Windows updates are installed and configured, then try again.
Download python-2.7.14 following link:
https://www.python.org/downloads/release/python-2714/
Install "python-2.7.14" and set PATH variable manual in windows.
Create a New folder in the root of windows drive -> windows ( for example C:\windows\ ) and name it "installer", it's done. install again. it worked for me.
When running python26 under windows OS (64bits).....
I have got errors like:
import win32api" error in Python 2.6: pywintypes26.dll
or
pythoncom26.dll missing
ImportError: DLL load failed: The specified module could not be found.
I have done the msi installation for python26
all dlls can be found under C:\Python26\Lib\site-packages\pywin32_system32
After I copy pywintypes26.dll and pythoncom26.dll from C:\Python26\Lib\site-packages\pywin32_system32 to C:\Python26\Lib\site-packages\win32 -> Solve the problem!
I also hit a problem importing win32api.
The post-install script for pywin32 failed, which should copy pythoncom26.dll, pythoncomloader26.dll, and pywintypes26.dll, among other things. I ran it by hand and my installation was fixed.
python scripts\pywin32_postinstall.py -install
I had a similar problem when installing under 64 bit Python 3.4.2. I ran the install executable pywin32‑219.win‑amd64‑py3.4.exe from http://www.lfd.uci.edu/~gohlke/pythonlibs/ .
On the site it states clearly:
"Python 3.4 users must manually run python.exe Scripts\pywin32_postinstall.py -install from an elevated command prompt."
which I did not do first time round; I installed from a normal prompt getting the following feedback:
c:\python34>python.exe Scripts\pywin32_postinstall.py -install
Copied pythoncom34.dll to C:\Python34\pythoncom34.dll
Copied pywintypes34.dll to C:\Python34\pywintypes34.dll
You do not have the permissions to install COM objects.
The sample COM objects were not registered.
etc.etc.
Finishing with "The pywin32 extensions were succesfully installed" ...
I only read the last sentence and I started to run some code resulting in getting these dll load fails.
So, did some research, and started an elevated prompt (how: see "http://www.sevenforums.com/tutorials/783-elevated-command-prompt.html") and again ran:
c:\python34>python.exe Scripts\pywin32_postinstall.py -install
Copied pythoncom34.dll to C:\Windows\system32\pythoncom34.dll
Copied pywintypes34.dll to C:\Windows\system32\pywintypes34.dll
Registered: Python.Interpreter
Registered: Python.Dictionary
Registered: Python
-> Software\Python\PythonCore\3.4\Help[None]=None
-> Software\Python\PythonCore\3.4\Help\Pythonwin Reference[None]='C:\\Python34\\Lib\\site-packages\\PyWin32.chm'
Pythonwin has been registered in context menu
Shortcut for Pythonwin created
Shortcut to documentation created
The pywin32 extensions were successfully installed.
And now my code runs happily (as far as this matter is concerned... sigh, so much other stuff to do).
Run the installer as Administrator and it works:
Right click on pywin32-installer.exe
Choose "Run as Administrator"
As suggested above the post install script is not run, this issue can be seen when installing from a wheel (As I encountered)
python scripts\pywin32_postinstall.py -install
If find you have this issue when installing via wheels, then installing it from here can solve the above issue.
https://pypi.python.org/pypi/pypiwin32
There appears to be a bug in the installer. The recommended workaround in the ticket is the same one as proposed by Dave Bremer.
I could fix this situation by removing all installed Python3.4 versions (had forgotten to uninstall 3.4.1 before installing 3.4.2), deleting C:\Python34 and after installing Python 3.4.2 pywin32-219.win32-py34.exe could be installed and called without problems.
So, copying around DLLs should NOT be necessary!
I always install the Active State Python distro which installs the win32 packages for you and gets it right.
If the above didn't fix the problem, you're still missing the msvcr100.dll file. It's either in your \System32\ folder, or more likely in your c:\PythonXX\Lib\site-packages\win32\ folder.
That fixed it for me after hours of search to no avail, even though it looks like the import still isn't resolved as it should be (PyCharm still gives me the squiggly underline), but it works.
First I was using pip to install pywin32 in anaconda environment, that's why no matter what I did it was failing. After trial and error, I figured out that
conda install pywin32
is the right way to install pywin32 in the anaconda package manager.
I don't know whether it's too late or not to answer this question. I also hit this problem, and I tried every method above, but neither of them worked.
Finally, I found the reason. When we install pywin32, we must choose the one that fits python's version(2.6， 2.7， 3.3， etc) and python's bit number(x64 or x86). Notice, it must fit python's bit number, not PC's bit number. If you install x86 python in a x64 PC, you have to install a pywin32 with x86.
In my case i had to copy pywintypes26.dll and pythoncom26.dll files into C:\Windows\System32 folder to work it properly in jupyter notebook.
I am using windows 10 OS with multiple python versions