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

qt and console Based Startup Errors #445

Closed
meawoppl opened this Issue May 17, 2011 · 3 comments

Comments

Projects
None yet
3 participants
@meawoppl

meawoppl commented May 17, 2011

I successfully installed the current master branch with the following:

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

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

Console:
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

QTConsole:
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
qt.qVersion()
'3.3.8b'

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.

@meawoppl

This comment has been minimized.

Show comment
Hide comment
@meawoppl

meawoppl May 17, 2011

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

meawoppl commented May 17, 2011

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 May 17, 2011

@minrk

This comment has been minimized.

Show comment
Hide comment
@minrk

minrk May 17, 2011

Member

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).

Member

minrk commented May 17, 2011

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).

@gourneau

This comment has been minimized.

Show comment
Hide comment
@gourneau

gourneau commented Mar 13, 2012

Thanks @meawoppl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment