Spyder: crash when starting fresh install of Spyder Anaconda 4.3!

[randomgambit]

Hello everyone,

Just installed the new Anaconda 4.3 (Python 2.7 version WIN64 installer) and I am not even able to start Spyder,

I am getting the cryptic message:

I am so sad. What is going on here?
Rebooted and reinstalled. Still the same. :(

[randomgambit]

@ccordoba12 @goanpeca please tell me everything is under control here! I want to use that version :D

[ccordoba12]

@randomgambit, some questions for you:

1. Did you install Anaconda in a directory with spaces or non-ascii characters on it (like tildes or non-english characters)?
2. Did you install Anaconda for all users in your computer or just you?

[randomgambit]

@ccordoba12 some answers for you:

1) I dont think so. my path is "C:\Users\mylogin\AppData\Local\Continuum\Anaconda2\pythonw.exe"
2) just for me

[ccordoba12]

And what is the output of

qmake -query

?

[randomgambit]

(C:\Users\m1hxb02\AppData\Local\Continuum\Anaconda2) C:\Users\mylogin>qmake -que
ry
QT_SYSROOT:
QT_INSTALL_PREFIX:C:/Users/ray/qtb-2.7-64/_b_env/Library
QT_INSTALL_ARCHDATA:C:/Users/ray/qtb-2.7-64/_b_env/Library
QT_INSTALL_DATA:C:/Users/ray/qtb-2.7-64/_b_env/Library
QT_INSTALL_DOCS:C:/Users/ray/qtb-2.7-64/_b_env/Library/doc
QT_INSTALL_HEADERS:C:/Users/ray/qtb-2.7-64/_b_env/Library/include/qt
QT_INSTALL_LIBS:C:/Users/ray/qtb-2.7-64/_b_env/Library/lib
QT_INSTALL_LIBEXECS:C:/Users/ray/qtb-2.7-64/_b_env/Library/bin
QT_INSTALL_BINS:C:/Users/ray/qtb-2.7-64/_b_env/Library/bin
QT_INSTALL_TESTS:C:/Users/ray/qtb-2.7-64/_b_env/Library/tests
QT_INSTALL_PLUGINS:C:/Users/ray/qtb-2.7-64/_b_env/Library/plugins
QT_INSTALL_IMPORTS:C:/Users/ray/qtb-2.7-64/_b_env/Library/imports
QT_INSTALL_QML:C:/Users/ray/qtb-2.7-64/_b_env/Library/qml
QT_INSTALL_TRANSLATIONS:C:/Users/ray/qtb-2.7-64/_b_env/Library/translations
QT_INSTALL_CONFIGURATION:
QT_INSTALL_EXAMPLES:C:/Users/ray/qtb-2.7-64/_b_env/Library/examples
QT_INSTALL_DEMOS:C:/Users/ray/qtb-2.7-64/_b_env/Library/examples
QT_HOST_PREFIX:C:/Users/ray/qtb-2.7-64/_b_env/Library
QT_HOST_DATA:C:/Users/ray/qtb-2.7-64/_b_env/Library
QT_HOST_BINS:C:/Users/ray/qtb-2.7-64/_b_env/Library/bin
QT_HOST_LIBS:C:/Users/ray/qtb-2.7-64/_b_env/Library/lib
QMAKE_SPEC:win32-msvc2008
QMAKE_XSPEC:win32-msvc2008
QMAKE_VERSION:3.0
QT_VERSION:5.6.2

(C:\Users\mylogin\AppData\Local\Continuum\Anaconda2) C:\Users\mylogin>

[ccordoba12]

Ok, so that's the problem.

@mingwandroid, what if we use a default qt.conf for the root environment to avoid this problem for most users? And use our post-install script when people wants to install Qt in a different environment?

I mean, I know that's not a real solution but I really don't know how else to improve this situation.

[randomgambit]

thanks @ccordoba12 ! Does your answer imply there is a quick fix for that problem (which is pretty radical --> I cannot even start Spyder once)

[ccordoba12]

By default qt.conf I mean a file whose paths are fixed and not computed depending on the installation directory.

[ccordoba12]

@randomgambit, I'm looking into it :-)

[randomgambit]

please post it there ASAP !!!!! :D hehe

[mingwandroid]

Need to figure out what's going on here..

[ccordoba12]

Ray, I have a solution for this, but I'll post it tomorrow (I've got to go to sleep :-)

[randomgambit]

whaaat!!! Cannot wait bro ! :D

[ccordoba12]

@mingwandroid, the solution is to work with relative paths in qt.conf and get rid of our post install script on Windows (and possibly other OSes, but Windows would be fine to start with because it's the one that's giving us more headaches :-).

So our qt package would install a qt.conf in Library\bin with these contents

[Paths] 
Prefix = .. 
Binaries = . 
Libraries = ../Library/lib
Headers = ../Library/include/qt

and our pyqt package would install another qt.conf in the root of the environment (i.e. next to python.exe and pythonw.exe) with these contents:

[Paths] 
Prefix = Library 
Binaries = Library/bin 
Libraries = Library/lib 
Headers = Library/include/qt

Since the contents of those files are fixed, we don't need our post install script anymore!

I tried those files in one of my environments and they seem to work as expected (at least Spyder and qtconsole start without problems). Unfortunately, I don't have time to test if pyqt compiles with these changes, but you could help me to try that :-)

[ccordoba12]

@randomgambit, the solution for you is to create a file named qt.confusing a text editor (e.g. Notepad++) in

C:\Users\m1hxb02\AppData\Local\Continuum\Anaconda2

with these contents

[Paths] 
Prefix = Library 
Binaries = Library/bin 
Libraries = Library/lib 
Headers = Library/include/qt

[ccordoba12]

@mingwandroid, sorry for not have thought about this before, but it just occurred to me last night!

[mingwandroid]

OK that's cool and I'm +1 on it so long as it works for hardlinked and symlinker environments but I need to know why post install scripts are not being run for some people with the 4.3 release.

It seems pretty urgent to get that fixed.

[randomgambit]

@mingwandroid @ccordoba12 whoa is it that simple?? great! but can't you have some sort of update via conda so that people can have the right file automatically?

[randomgambit]

@mingwandroid @ccordoba12 it worked! cannot believe it! that s great. Is there any way this fix can mess up with my packages or the overall functioning of the program?

[mingwandroid]

@mingwandroid @ccordoba12 whoa is it that simple?? great! but can't you have some sort of update via conda so that people can have the right file automatically?

The installer already does try to write this file.

Is there any way this fix can mess up with my packages or the overall functioning of the program?

No.

[mingwandroid]

OK I found the problem. I'll add it to the agenda for the team meeting today.

[ccordoba12]

So are we going to have Anaconda 4.3.1 to fix this?

[goanpeca]

Yep, new release coming I believe

[ccordoba12]

Ray, we should try to add to that release my proposed fix for qt.conf

Do you think it is feasible?

[ccordoba12]

I'm closing this one as it is fixed.

[mingwandroid]

Hey @ccordoba12, since I got to the root cause of the problem (it was an issue in constructor where it attempted to do binary prefix replacement on Windows causing the post install to not even run).

Now the post install gets run and it does the right thing so I think we are fine. It was decided to make the only the least amount of changes necessary to fix this issue for the new release as we didn't want to run it through the complete QA cycle so the only change is literally 2 lines of Python to _install.py.

[randomgambit]

@ccordoba12 @mingwandroid @goanpeca Hello there.

Unfortunately I just discovered a fatal bug in this new release. Just clicking on maximize current pane will crash Spyder beyond repair.

This is the message I get when I clink on the pane button

Spyder Internal Console

This console is used to report application
internal errors and to inspect Spyder
internals with the following commands:
  spy.app, spy.window, dir(spy)

Please don't use it to run your code

>>> WARNING:traitlets:kernel died: 6.01600003242
WARNING:traitlets:kernel died: 6.0110001564
WARNING:traitlets:kernel died: 6.00899982452
WARNING:traitlets:kernel died: 6.00600004196
WARNING:traitlets:kernel died: 6.00599980354
WARNING:traitlets:kernel died: 6.00999999046
Traceback (most recent call last):
  File "C:\Users\mylogin\AppData\Local\Continuum\Anaconda2\lib\site-packages\spyder\app\mainwindow.py", line 2202, in maximize_dockwidget
    self.last_plugin.dockwidget.toggleViewAction().setDisabled(True)
AttributeError: 'NoneType' object has no attribute 'dockwidget'

Any ideas?
Thanks!!

[goanpeca]

@randomgambit I think this has been solved by https://github.com/spyder-ide/spyder/pull/4109

And will come in the next bugfix release

[randomgambit]

thanks @goanpeca that s good to know. Is there any quick and dirt fix for that like the small txt file @ccordoba12 created for the original bug above? Maximizing the pane is pretty important to me... Thanks!

[nbmehar]

@ccordoba12 I can't fix it. I made the file qt.conf with the exact contents you have mentioned, using notepad.

But I couldn't find the folder continuum anywhere.

I did find these files which are from anaconda.So I pasted the file here.

and also in the installed directory over here, but when I pasted the file, it asked me to replace the existing file. I replaced it.

I still couldn't run it