[sage-devel] Re: sage + py.test fails

2008-07-21 Thread Ondrej Certik
We officially reported the bug to them via their tracker. Then one Sage developer worked for a long time and heroically found a fix and reported it too. I think it maybe just takes a long time to filter through the system back to the *deployed* RHEL and SLES linux boxes all over the place.

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread William Stein
On Sat, Jul 19, 2008 at 10:44 PM, Ondrej Certik [EMAIL PROTECTED] wrote: Hi, when testing sage 3.0.5 using py.test, sage fails to import, because it's using input (?) stream's write and flush methods: I don't know what py.test is, but do you really need to use the IPython interface to sage

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread Ondrej Certik
On Sun, Jul 20, 2008 at 1:36 PM, William Stein [EMAIL PROTECTED] wrote: On Sat, Jul 19, 2008 at 10:44 PM, Ondrej Certik [EMAIL PROTECTED] wrote: Hi, when testing sage 3.0.5 using py.test, sage fails to import, because it's using input (?) stream's write and flush methods: I don't know

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread William Stein
On Sun, Jul 20, 2008 at 3:57 PM, Ondrej Certik [EMAIL PROTECTED] wrote: On Sun, Jul 20, 2008 at 1:36 PM, William Stein [EMAIL PROTECTED] wrote: On Sat, Jul 19, 2008 at 10:44 PM, Ondrej Certik [EMAIL PROTECTED] wrote: Hi, when testing sage 3.0.5 using py.test, sage fails to import, because

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread Ondrej Certik
On Sun, Jul 20, 2008 at 4:05 PM, William Stein [EMAIL PROTECTED] wrote: On Sun, Jul 20, 2008 at 3:57 PM, Ondrej Certik [EMAIL PROTECTED] wrote: On Sun, Jul 20, 2008 at 1:36 PM, William Stein [EMAIL PROTECTED] wrote: On Sat, Jul 19, 2008 at 10:44 PM, Ondrej Certik [EMAIL PROTECTED] wrote:

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread William Stein
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

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread Ondrej Certik
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

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread Ondrej Certik
On Sun, Jul 20, 2008 at 5:20 PM, Ondrej Certik [EMAIL PROTECTED] wrote: 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

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread William Stein
There must be a way to get this fixed, so that Sage can be used as a library and it can use it's own compiled libs, but it will not force the rest of the system to use them. Or there isn't? There pretty much isn't. However you can maybe do: sage: os.system('unset LD_LIBRARY_PATH; gedit')

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread William Stein
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

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread Ondrej Certik
On Sun, Jul 20, 2008 at 5:45 PM, William Stein [EMAIL PROTECTED] wrote: There must be a way to get this fixed, so that Sage can be used as a library and it can use it's own compiled libs, but it will not force the rest of the system to use them. Or there isn't? There pretty much isn't.

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread mabshoff
On Jul 20, 8:20 am, Ondrej Certik [EMAIL PROTECTED] wrote: On Sun, Jul 20, 2008 at 4:48 PM, William Stein [EMAIL PROTECTED] wrote: Hi, SNIP 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

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread Ondrej Certik
On Sun, Jul 20, 2008 at 10:02 PM, mabshoff [EMAIL PROTECTED] wrote: On Jul 20, 11:20 am, Ondrej Certik [EMAIL PROTECTED] wrote: On Sun, Jul 20, 2008 at 6:38 PM, mabshoff [EMAIL PROTECTED] wrote: SNIP Hi Ondrej, But even then it will only be a question of time until something else

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread mabshoff
On Jul 20, 11:20 am, Ondrej Certik [EMAIL PROTECTED] wrote: On Sun, Jul 20, 2008 at 6:38 PM, mabshoff [EMAIL PROTECTED] wrote: SNIP Hi Ondrej, But even then it will only be a question of time until something else blows up. That is why I strictly refuse to support Sage being used in

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread William Stein
On Sun, Jul 20, 2008 at 11:23 PM, mabshoff [EMAIL PROTECTED] wrote: On Jul 20, 1:22 pm, Ondrej Certik [EMAIL PROTECTED] wrote: SNIP Hi Ondrej, Nope, it does not work for example on OSX. With a python 2.5.2 on I don't understand the OSX problems about universal/non universal python

[sage-devel] Re: sage + py.test fails

2008-07-20 Thread Ondrej Certik
On Sun, Jul 20, 2008 at 6:38 PM, mabshoff [EMAIL PROTECTED] wrote: On Jul 20, 8:20 am, Ondrej Certik [EMAIL PROTECTED] wrote: On Sun, Jul 20, 2008 at 4:48 PM, William Stein [EMAIL PROTECTED] wrote: Hi, SNIP BTW, here is another creepy thing, that maybe is a bug in Sage: $ gedit gedit: