Shell: error → unusable

[Greg Couch]

The following bug report has been submitted:
Platform:        Linux-4.15.0-38-generic-x86_64-with-debian-buster-sid
ChimeraX Version: 0.8 (2018-09-28)
Description
The Shell tool becomes unusable after an exception is thrown.  For example, import a nonexistent module.  Then type in anything else and get "ERROR: execution aborted"

Log:
UCSF ChimeraX version: 0.8 (2018-09-28)  
How to cite UCSF ChimeraX  

toolshed show sh

toolshed show sh

/home/gregc/src/chimerax/ChimeraX.app/lib/python3.6/site-
packages/IPython/core/history.py:226: UserWarning: IPython History requires
SQLite, your history will not be saved  
warn("IPython History requires SQLite, your history will not be saved")  

toolshed show "Bug Reporter"

toolshed show "Bug Reporter"

toolshed show Shell

toolshed show Shell




OpenGL version: 4.5 (Core Profile) Mesa 18.0.5
OpenGL renderer: AMD TAHITI (DRM 2.50.0 / 4.15.0-38-generic, LLVM 6.0.0)
OpenGL vendor: X.Org

[Eric Pettersen]

This is because the qtconsole package pulls in ipython7 instead of ipython6. Tom Goddard had thought that he fixed this by going from qtconsole 4.4.1 to 4.4.2, (which seem to revert to ipython6). It seems that this fix was just a fluke, since 4.4.2 is now bringing in ipython7. Not sure what to do about it.

[Tristan Croll]

I may as well report this other annoyance with the new iPython version here (since it's not really worth filing a new report over): it's no longer possible to define functions or loops with more than one line on-the-fly. For example:

for i in range(10):
    print(i) # Pressing <Enter> here will run the loop, rather than starting a new indented line

[Eric Pettersen]

qtconsole brings in ipykernel>=4.1 which in turn brings in ipython>=4.0.0

Can we preempt that by install ipython 6 ourselves first?

--Eric

[Eric Pettersen]

Apparently you can force installation of older prereqs. I forced installation of a set of versions that I knew worked:

qtconsole 4.4.1
ipykernel 4.9.0
ipython 6.5.0

That worked. I've committed changes to force those versions. My testing seems to indicate that it's ipykernel >= 5 (specifically 5.1.0) thats the actual culprit. We will need to revisit from time to time to see if even newer versions fix the problem.