From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] [sage-on-gentoo] ImportError: No module named CrashHandler
Date: Thu, 26 Jan 2012 11:19:14 -0600 [thread overview]
Message-ID: <20120126111914.30eec62f@ledaig.d.umn.edu> (raw)
In-Reply-To: <20120126165855.8fd4f36a.v_2e@ukr.net>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
Hi Vladimir,
You could try:
https://github.com/cschwan/sage-on-gentoo/issues/93
In the issue there was an IPython-0.10.1-py-2.7.egg-info file that was floating around. However, if this fixes things, it's odd that it's appearing again with 4.8, unless your ipython was recently upgraded?
Steve
On Thu, 26 Jan 2012 16:58:55 +0200
v_2e@ukr.net wrote:
> ----------------------------------------------------------------------
> Hello!
> After upgrade to Sage 4.8 I cannot start it and get the following
> error message:
>
>
> | Sage Version 4.8, Release Date: 2012-01-20 |
> | Type notebook() for the GUI, and license() for information. |
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "/usr/bin/sage-ipython", line 19, in <module>
> from IPython.CrashHandler import CrashHandler
> ImportError: No module named CrashHandler
>
>
> Is it a known issue? If it is, what is the solution?
>
> Thanks.
> Vladimir
>
> -----
> <v_2e@ukr.net>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-01-26 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 14:58 [gentoo-science] [sage-on-gentoo] ImportError: No module named CrashHandler v_2e
2012-01-26 17:19 ` Steven Trogdon [this message]
2012-01-26 23:04 ` [gentoo-science] " v_2e
2012-01-26 23:37 ` Steven Trogdon
2012-01-27 2:47 ` fbissey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120126111914.30eec62f@ledaig.d.umn.edu \
--to=strogdon@d.umn.edu \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox