Skip to content


Subversion checkout URL

You can clone with
Download ZIP


qt and console Based Startup Errors #445

meawoppl opened this Issue · 3 comments

3 participants


I successfully installed the current master branch with the following:

python: 2.6.5 (r265:79063, Apr 16 2010, 13:09:56) [GCC 4.4.3]
platform: linux2

sphinx: Not found (required for building documentation)
pygments: 1.2.2
nose: 0.11.1
pexpect: 2.3
pyzmq: 2.1dev
readline: yes

meawoppl@meawoppl-leela:~$ ipython
Traceback (most recent call last):
File "/usr/local/bin/ipython", line 8, in
from IPython.frontend.terminal.ipapp import launch_new_instance
ImportError: No module named terminal.ipapp

meawoppl@meawoppl-leela:~$ ipython-qtconsole
Traceback (most recent call last):
File "/usr/local/bin/ipython-qtconsole", line 4, in
from IPython.frontend.qt.console.ipythonqt import main
ImportError: No module named qt.console.ipythonqt

import qt

The WX based console seems to work fine . . . only producing a waring about a default config file:
Could not open Options.conf, defaulting to default values.


This was caused by a conflicting (ubuntu installed) ipython. Hard to debug, is there some way to warn during config step?

@meawoppl meawoppl closed this

Yes, I suppose we can print a message during build if an older IPython is found. The problem is, with Python this is perfectly valid - you can have a dozen versions of IPython installed, and if you do, it's up to you to keep them in order.

The diagnosis is (for all Python modules, not just IPython): if a script raises ImportErrors on its own packages, the most likely culprit is that the startup script on your PATH does not match the first package found on your PYTHONPATH (or sys.path).

@damianavila damianavila referenced this issue from a commit
Commit has since been removed from the repository and is no longer available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.