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 what py.test is, but do you really need to use the IPython > interface to sage with it? Instead of running Sage could you do > > sage -python > > then put > > from sage.all import * > > or something? This comment may be completely off, since I > don't know what py.test is. Hey, what's py.test?
http://codespeak.net/py/dist/test.html it used to be the only good testing framework in python, now there is also nosetests: http://www.somethingaboutorange.com/mrl/projects/nose/ that is probably better, and the above problem doesn't arise in there. But as usual, nosetests and py.test are not equivalent, so we need to adapt some of our tests first. sage -python doesn't work: $ sage -python /usr/bin/py.test sympy/test_external/test_sage.py Traceback (most recent call last): File "/usr/bin/py.test", line 9, in <module> import py ImportError: No module named py You would have to set up paths to the system wide modules first. I want to use system wide python, not Sage's python. Ondrej --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
