Re: [sage-support] Re: Bug in list_plot3d?

2012-04-03 Thread P Purkayastha
On 04/04/2012 10:11 AM, kcrisman wrote: On Sunday, April 1, 2012 3:56:41 AM UTC-4, P Purkayastha wrote: If I plot 2 points using list_plot3d, then they are correctly joined by a line. If I increase the number of points to 3, then I don't get a plane and instead get a bizarre shape

Re: [sage-support] Re: Primary decomposition

2012-04-03 Thread Vinay Wagh
Yes, this is not yet implemented in Singular yet. Although GTZ algorithm gives error whereas SY algorithm clearly mentions "Not implemented". If you are interested in char 0, and not specifically Complex, then using QQ instead of CC gives a workaround. As far as your example is concerned, it may n

[sage-support] Re: Primary decomposition

2012-04-03 Thread Dima Pasechnik
On Wednesday, 4 April 2012 10:28:42 UTC+8, vasu wrote: > > Hi > I am trying to run the following piece of code on sage > > > R. = CC['x,y,z'] > I = (x-(y*z), y-(x*z), x*y)*R; I > > I.primary_decomposition() > > and I seem to be getting the following error: > > Traceback (most recent call last): >

[sage-support] Primary decomposition

2012-04-03 Thread vasu
Hi I am trying to run the following piece of code on sage R. = CC['x,y,z'] I = (x-(y*z), y-(x*z), x*y)*R; I I.primary_decomposition() and I seem to be getting the following error: Traceback (most recent call last): File "", line 1, in File "_sage_input_9.py", line 10, in exec compile

[sage-support] Re: sagetex question

2012-04-03 Thread Jason Grout
On 4/3/12 9:16 PM, kcrisman wrote: On Tuesday, April 3, 2012 10:14:01 PM UTC-4, Jason Grout wrote: On 4/3/12 8:35 PM, kcrisman wrote: > > > On Friday, March 30, 2012 9:45:21 PM UTC-4, Dan Drake wrote: > > On Fri, 30 Mar 2012 at 11:24AM -0700, Tom Judson wrote:

[sage-support] Re: sagetex question

2012-04-03 Thread kcrisman
On Tuesday, April 3, 2012 10:14:01 PM UTC-4, Jason Grout wrote: > > On 4/3/12 8:35 PM, kcrisman wrote: > > > > > > On Friday, March 30, 2012 9:45:21 PM UTC-4, Dan Drake wrote: > > > > On Fri, 30 Mar 2012 at 11:24AM -0700, Tom Judson wrote: > > > I have a question about sagetex. Is it pos

[sage-support] Re: contour_plot region option

2012-04-03 Thread kcrisman
On Tuesday, April 3, 2012 4:06:06 PM UTC-4, Jason Grout wrote: > > On 4/3/12 2:55 PM, Antonio Russo wrote: > > Hello. I would like to be able to do an implicit_plot, but only inside a > particular region (much like is allowed with implicit_plot3d, with its > region option). I seem to be having

[sage-support] Re: sagetex question

2012-04-03 Thread Jason Grout
On 4/3/12 8:35 PM, kcrisman wrote: On Friday, March 30, 2012 9:45:21 PM UTC-4, Dan Drake wrote: On Fri, 30 Mar 2012 at 11:24AM -0700, Tom Judson wrote: > I have a question about sagetex. Is it possible to run sagetex if you are > using a remote server as opposed to a local co

[sage-support] Re: Bug in list_plot3d?

2012-04-03 Thread kcrisman
On Sunday, April 1, 2012 3:56:41 AM UTC-4, P Purkayastha wrote: > > If I plot 2 points using list_plot3d, then they are correctly joined by a > line. If I increase the number of points to 3, then I don't get a plane and > instead get a bizarre shape with a "floor" suddenly appearing out of > n

Re: [sage-support] sagetex question

2012-04-03 Thread kcrisman
On Friday, March 30, 2012 9:45:21 PM UTC-4, Dan Drake wrote: > > On Fri, 30 Mar 2012 at 11:24AM -0700, Tom Judson wrote: > > I have a question about sagetex. Is it possible to run sagetex if you > are > > using a remote server as opposed to a local copy of sage. I run sagetex > > locally on

[sage-support] Re: contour_plot region option

2012-04-03 Thread Jason Grout
On 4/3/12 2:55 PM, Antonio Russo wrote: Hello. I would like to be able to do an implicit_plot, but only inside a particular region (much like is allowed with implicit_plot3d, with its region option). I seem to be having trouble using Sage's revision control system (which is why this patch is n

[sage-support] contour_plot region option

2012-04-03 Thread Antonio Russo
Hello. I would like to be able to do an implicit_plot, but only inside a particular region (much like is allowed with implicit_plot3d, with its region option). I seem to be having trouble using Sage's revision control system (which is why this patch is not in the standard form), but that is anot

Re: [sage-support] Re: importing .so files

2012-04-03 Thread Emil
Ah.. my current working directory had a foo/ directory, which was causing everything to go wrong, because it was trying to get things from there instead of site-packages/foo. The main remaining problem is how to get the Cython extension class foo.bar.Bar to appear as foo.bar.Bar instead of bar

Re: [sage-support] Re: importing .so files

2012-04-03 Thread Emil
On 3 April 2012 17:06, Dima Pasechnik wrote: > Probably. You can see what Sage does in this regard by looking > at the value of LD_LIBRARY_PATH in Sage shell > (i.e. when you run sage -sh) Doing this reveals $LD_LIBRARY_PATH to contain /usr/local/sage/local/lib/R/lib:/usr/local/sage/local/lib/op

[sage-support] Re: importing .so files

2012-04-03 Thread Dima Pasechnik
On 2012-04-03, Emil wrote: > Hi, I have a Python package, 'foo' that I can install with distutils, > into Sage's site-packages directory. It contains a Cython file, > 'bar.pyx'. Now, if in the setup.py file, I have > > Extension('bar', ...) > > then everything works fine, except that 'bar.so' gets

Re: [sage-support] Re: %cython failing in notebook because of accessing the wrong directory

2012-04-03 Thread Priyanka Kapoor
On Tue, Apr 3, 2012 at 1:31 AM, Maarten Derickx wrote: > In your setup everything worked ok. You just defined a function called > hello. The function was never executed so you didn't see anything. > To execute the function try the following: > > hello() Ok > Considdering you are new with sage I

[sage-support] importing .so files

2012-04-03 Thread Emil
Hi, I have a Python package, 'foo' that I can install with distutils, into Sage's site-packages directory. It contains a Cython file, 'bar.pyx'. Now, if in the setup.py file, I have Extension('bar', ...) then everything works fine, except that 'bar.so' gets put in site-packages, rather than site-