[sage-devel] Re: Notebook problem with sympy

2009-04-09 Thread Robert Bradshaw
On Apr 9, 2009, at 11:31 AM, mabshoff wrote: > On Apr 9, 11:01 am, Ondrej Certik wrote: >> On Thu, Apr 9, 2009 at 10:33 AM, Arnaud Bergeron >> wrote: > > > >>> Or simply, to keep the existing simplicity, change %myhandler to >>> call >>> sage_myhandler and rename the existing ones. There

[sage-devel] Re: Notebook problem with sympy

2009-04-09 Thread mabshoff
On Apr 9, 11:01 am, Ondrej Certik wrote: > On Thu, Apr 9, 2009 at 10:33 AM, Arnaud Bergeron wrote: > > Or simply, to keep the existing simplicity, change %myhandler to call > > sage_myhandler and rename the existing ones.  There is very little > > probability of other projects using sage_ a

[sage-devel] Re: Notebook problem with sympy

2009-04-09 Thread Ondrej Certik
On Thu, Apr 9, 2009 at 10:33 AM, Arnaud Bergeron wrote: > > 2009/4/7 Brian Granger : >> >>> That seems awfully complicated.  How about (untested): >>> >>> sage_python = python >>> from sympy import * >>> python = sage_python >>> >>> or (even shorter, and still untested): >>> >>> from sympy import

[sage-devel] Re: Notebook problem with sympy

2009-04-09 Thread Arnaud Bergeron
2009/4/7 Brian Granger : > >> That seems awfully complicated.  How about (untested): >> >> sage_python = python >> from sympy import * >> python = sage_python >> >> or (even shorter, and still untested): >> >> from sympy import * >> restore('python') > > Sure these may work, but in my mind they ar

[sage-devel] Re: Notebook problem with sympy

2009-04-07 Thread Brian Granger
> That seems awfully complicated.  How about (untested): > > sage_python = python > from sympy import * > python = sage_python > > or (even shorter, and still untested): > > from sympy import * > restore('python') Sure these may work, but in my mind they are temporary hacks. > The %whatever synt

[sage-devel] Re: Notebook problem with sympy

2009-04-07 Thread Ondrej Certik
On Tue, Apr 7, 2009 at 1:26 PM, Carl Witty wrote: > > On Tue, Apr 7, 2009 at 12:16 PM, Brian Granger > wrote: >> >> Ahh, that makes sense.  It is the sympy.python thing that causes the >> problem.  This hack seems to work fix the issue in the notebook: >> >> import sympy >> sympy.sage_python =

[sage-devel] Re: Notebook problem with sympy

2009-04-07 Thread Carl Witty
On Tue, Apr 7, 2009 at 12:16 PM, Brian Granger wrote: > > Ahh, that makes sense.  It is the sympy.python thing that causes the > problem.  This hack seems to work fix the issue in the notebook: > > import sympy > sympy.sage_python = sympy.python > del sympy.python > from sympy import * > > But an

[sage-devel] Re: Notebook problem with sympy

2009-04-07 Thread Ondrej Certik
On Tue, Apr 7, 2009 at 12:16 PM, Brian Granger wrote: > > Ahh, that makes sense.  It is the sympy.python thing that causes the > problem.  This hack seems to work fix the issue in the notebook: > > import sympy > sympy.sage_python = sympy.python > del sympy.python > from sympy import * > > But an

[sage-devel] Re: Notebook problem with sympy

2009-04-07 Thread Brian Granger
Ahh, that makes sense. It is the sympy.python thing that causes the problem. This hack seems to work fix the issue in the notebook: import sympy sympy.sage_python = sympy.python del sympy.python from sympy import * But any code in sympy that uses sympy.python will now fail. Really this is a b

[sage-devel] Re: Notebook problem with sympy

2009-04-07 Thread Ondrej Certik
On Tue, Apr 7, 2009 at 11:01 AM, Brian Granger wrote: > > Hi, > > I am using the sage 3.2.3 notebook.  I am using it in python mode and > am having trouble with sympy: > > from sympy import * > x = var('x') > > Traceback (most recent call last): >  File "", line 1, in >  File "/Users/bgranger/.s