On Sun, Jul 20, 2008 at 4:48 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> On Sun, Jul 20, 2008 at 4:34 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>>> If you're using the system-wide python why does Sage's copy of
>>> IPython have anything to do with anything? I guess I'm basically
>>> asking why you are having to program around a problem with
>>> Ipython in order to do some sort of testing with Sage? For example,
>>> when Sage's doctests run IPython is never involved at all; it's
>>> not even imported.
>>
>> I don't want to have anything in common with ipython, but sage invokes
>> it on import sage.all, as can be checked easily:
>
> Wow, that sucks. Thanks for pointing this out!! It is a major bug which
> i'll fix asap:
>
> http://trac.sagemath.org/sage_trac/ticket/3685
>
> Thanks again -- I really appreciate this.
Thanks too.
BTW, here is another creepy thing, that maybe is a bug in Sage:
$ gedit
gedit: symbol lookup error: /usr/lib/libxml2.so.2: undefined symbol: gzopen64
$
I was just about to report this as a grave bug in Debian, but before I did:
$ ldd /usr/lib/libxml2.so.2
linux-gate.so.1 => (0xb7f92000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7e4e000)
libz.so.1 => /home/ondra/ext/sage/local/lib/libz.so.1 (0xb7e38000)
libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7e11000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7cb6000)
/lib/ld-linux.so.2 (0xb7f93000)
so I just removed the line:
export LD_LIBRARY_PATH=/home/ondra/ext/sage/local/lib
from my bashrc and all works again. So this is not the way how to
setup sage. It's actually quite annoying, that you can use either Sage
or gedit, but not both in the same terminal. Ok, you may say forget
about systemwide python, just use Sage as it is, take it or leave it.
Ok, first, it's not the way I'd like to work, but ok, but it won't
allow me to use gedit either... Try this:
sage: os.system("xclock")
0
this works anc xclock comes up, but this doesn't:
sage: os.system("gedit")
** (gedit:26452): WARNING **: Error initializing Python interpreter:
could not import pygtk.
** (gedit:26452): WARNING **: Please check the installation of all the
Python related packages required by gedit and try again.
** (gedit:26452): WARNING **: Cannot load Python plugin 'Python
Console' since gedit was not able to initialize the Python
interpreter.
gedit: symbol lookup error: /usr/lib/libxml2.so.2: undefined symbol: gzopen64
32512
I don't know, but I think Sage should not be messing with my system.
So this makes me think that maybe exporting the variables so that they
work in the whole terminal (thus allowing me to use systemwide python)
is not a good thing, unless there is a robust way to fix the above
problems. I'll try to investiage the other way round then, e.g.
setting up paths in sage, so that it imports my systemwide library and
the current revision of sympy, that I want to test. But I don't like
this at all, because this makes Sage a full blown application, not a
library, that can be reused in other projects.
Ondrej
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
