New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spyder crashes at startup in new conda environment python 3.4 on Windows 8.1 x64 #2858
Comments
A colleague here has the same problem, but it was after an update, not a new environment. I tried to reset the preferences but it didn't change anything. |
@silicium14, thanks for the detailed report. It seems that Qt was not compiled correctly for Python 3.4 by Continuum. I also found this error while testing other things last night. However, this is not a Spyder bug because Spyder runs fine in Python 2.7 and 3.5 environments. I'll report this problem with my coworkers at Continuum and see if we can solve it soon. |
I was having a similar problem. Using the above information, I ran I am running Windows 7 with Anaconda where the root is python 3.5 and the installed environment is python 3.4. Spyder ran fine on the root and |
@timctran , Thanks ! Your solution works! |
Thanks @timctran! I had the same problem on Windows 7 x64. |
@timctran |
I would be glad to helping solving this problem. Spyder failed to start occasionally when I update anaconda or matplotlib. |
Yeah thanks heaps @timctran this fixed the spyder launch error for me too. Windows 10 64 bit. |
@timctran One note that maybe of interest before installing qt=4.8.7=vc10_4 the package was downgraded from qt=4.8.7=vc10_5. So it seems that 10_5 maybe at the root of the problem. |
@ccordoba12 Has in been fixed in Anaconda ? |
@timctran Thanks a lot!!! Made my day! |
I get something very similar on Windows 7 x64 with Spyder 3.0.1, Python 3.4.5 and qt 4.8.7-vc10_9 from anaconda. I think this is what is behind the hanging automatic test of spyder-unittest with this configuration, as shown in the corresponding log. |
@timctran thank you. Additionally i did
|
Closing because this is not really a Spyder bug. Also, please Qt5 instead of Qt4. |
C:\Users\Khushboo>spyder --show-console facing error while running spyder through command prompt |
@timctran Thank you! This solves the problem. |
(1). The bug
I create a new environment with
conda create --name testspyder python=3.4 spyder
then I
activate testspyder
. When I don't specify spyder version, 2.3.8 is installed (spyder=2.3.8=py34_0
).When I try to start spyder in this environment, it crashes at startup, showing a Windows popup saying
python.exe has stopped working
. There is no console output with--show-console
.When I try to debug it with Microsoft Visual Studio 2015 (suggested to me by the debug button in the Windows popup), the following message appears:
According to this message the problem seems to be related to Qt.
The same problem occurs with spyder 2.3.7 (
spyder=2.3.7=py34_3
):(2). Package version comparison
My spyder 2.3.7 is running OK in my "stable" environment. This stable environment is created with installing the anaconda meta package. From continuum.io:
I decided to make 2 packages versions comparison:
conda create --name testspyder python=3.4 spyder
(2.3.8)conda create --name testspyder python=3.4 spyder=2.3.7
I only listed the packages common to the 2 compared environments AND with different versions.
conda create --name testspyder python=3.4 spyder
conda create --name testspyder python=3.4 spyder=2.3.7
I hope this helps. If this is not a spyder bug, then I hope this will help to identify the Qt / PyQt / ? bug.
This issue seems to be differs from #2834 since PyQwt is not installed in any of the 3 environments I present.
The text was updated successfully, but these errors were encountered: