[sage-devel] Re: MATLAB: viable alternative...?

2011-09-05 Thread David Ketcheson
I may have been too harsh in using the term 'disaster'. I am certainly glad that scipy exists, but I use it with extreme caution. First, it is quite disorganized. Say you want to solve an ODE. First, you have to know to import scipy.integrate (importing scipy doesn't give you scipy.integrate, fo

[sage-devel] Re: MATLAB: viable alternative...?

2011-08-31 Thread David Ketcheson
Qualifications to answer this question: -I have used MATLAB for 10 years in my research -About 3 years ago, I mostly switched to Python+numpy/scipy/ matplotlib, and I lead a project that includes about a dozen people developing code in Python -I use SAGE (mainly the notebook) in my teaching. Fo

[sage-devel] Re: A Sage NSF proposal to the Computational Mathematics Program

2009-11-22 Thread David Ketcheson
I'm excited to see a major focus on numerics and PDEs in Sage. I'm thinking of using Sage to teach numerical methods for PDEs here at KAUST next semester. -David On Nov 20, 3:24 pm, William Stein wrote: > Hi, > > Me and several people have been putting together a proposal to this NSF > progra

[sage-devel] Re: importing non-sage modules in doctests

2008-08-30 Thread David Ketcheson
e errors. It doesn't include the contents of my SAGE_PYTHONPATH. If you know where the PYTHONPATH is set for 'sage - t', could you add a request to modify that in the trac ticket too? -David On Aug 30, 8:56 pm, mabshoff <[EMAIL PROTECTED]> wrote: > On Aug 30, 8:51 pm, David

[sage-devel] Re: importing non-sage modules in doctests

2008-08-30 Thread David Ketcheson
This works, but doesn't seem like a good solution, and is, I think, another good reason to allow the user to modify sage's startup pythonpath. -David On Aug 30, 8:32 pm, David Ketcheson <[EMAIL PROTECTED]> wrote: > Sorry for not being clear.  myfoo.py is the file with the do

[sage-devel] Re: importing non-sage modules in doctests

2008-08-30 Thread David Ketcheson
AIL PROTECTED]> wrote: > On Aug 30, 2008, at 3:33 PM, David Ketcheson wrote: > > > > > > > I'm developing a package and trying to use sage -t to automatically > > test examples I've put in the docstrings.  On the documentation page > > athttp://www.sagema

[sage-devel] importing non-sage modules in doctests

2008-08-30 Thread David Ketcheson
I'm developing a package and trying to use sage -t to automatically test examples I've put in the docstrings. On the documentation page at http://www.sagemath.org/doc/prog/node29.html it says I can do something like """ EXAMPLES: sage: from foo import * """ where foo is not part of

[sage-devel] Re: Sage Bug Report

2008-08-28 Thread David Ketcheson
ntually do everything? Will Sympy functionality replace var? -David On Aug 28, 10:07 am, "William Stein" <[EMAIL PROTECTED]> wrote: > On Thu, Aug 28, 2008 at 9:54 AM, Robert Bradshaw > > > > <[EMAIL PROTECTED]> wrote: > > > On Aug 27, 2008, at 1:54 P

[sage-devel] Re: Sage Bug Report

2008-08-27 Thread David Ketcheson
Thanks for the nice fix. I've managed to break things in a new way: >>> sage: from sympy import Symbol sage: x,y=Symbol('x',False),Symbol('y',False) sage: 1/2+y*x x*y + 1/2 sage: y*x+1/2 1/2 + y*x <<< The 'False' argument to Symbol here means the symbols are non- commutative. Adding a rational

[sage-devel] Sage Bug Report

2008-08-26 Thread David Ketcheson
The following input: from sympy import Symbol QQ(1)+Symbol('x')*QQ(2) produces an error: TypeError Traceback (most recent call last) /Applications/sage/ in () /Applications/sage/element.pyx in sage.structure.element.ModuleElement.__add__ (sage/structure/element