> What is your opinion?
> Can anyone unravel details about how this will be implemented? RPy maybe?
I am almost finished with a pexpect interface so that you can use R
just like any of the other programs that Sage has interfaces for
(Maple, Mathematica, Magma, etc.). I also have an experimental s
I mostly agree with the things stated above, and sage.calculus is clearly an
important part for applications.
Still, we should also consider other possible uses. I recently talked to
Michael Abshoff about whether we are planning to make R a part of SAGE. He
told me that William was convinced that i
On 31/10/2007, Bill Hart <[EMAIL PROTECTED]> wrote:
>
> On page 45 of Paul's slides, you have:
>
> Ne pas reinventer la roue
... which was amusing, given that Bill A's talk (the one right before
Paul Z's) had all been about reinventing the wheel! Of course, when
Paul said that my thoughts turned
On page 45 of Paul's slides, you have:
Ne pas reinventer la roue
Bill.
On 30 Oct, 23:42, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi Sage-devel,
>
> The talks linked to below are very interesting. In particular,
> see the talk by Paul Zimmerman (the MPFR guy) for a history of
> pari with l
On Oct 30, 6:29 pm, Carl Witty <[EMAIL PROTECTED]> wrote:
> On Oct 30, 1:48 pm, Robert Bradshaw <[EMAIL PROTECTED]>
> wrote:
>
> > This is due to the inplace operator stuff using refcounts to
> > determine if it's safe to mutate. The simple workaround is to not use
> > numpy arrays of SAGE objects
Robert Bradshaw wrote:
Hi Robert,
> I had an error like this and it turned out to be caused by a GC
> error. Specifically, an object A was allocated, then erroneously
> deallocated (but there was still stuff pointing to it). Object B was
> then allocated, with memory overlapping that of object
On Oct 31, 3:11 am, Carl Witty <[EMAIL PROTECTED]> wrote:
> On Oct 29, 10:11 am, Robert Bradshaw <[EMAIL PROTECTED]>
> wrote:
Hello,
>
> > There is another way that Py_ssize_t differs from int, namely that
> > Cython casting happens via the __index__ rather than __int__
> > function. __int__ i
On Oct 29, 10:11 am, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> There is another way that Py_ssize_t differs from int, namely that
> Cython casting happens via the __index__ rather than __int__
> function. __int__ is potentially bad because it tries to hard to cast
> to an int (e.g. truncating,
On Oct 30, 1:48 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> This is due to the inplace operator stuff using refcounts to
> determine if it's safe to mutate. The simple workaround is to not use
> numpy arrays of SAGE objects. Another question is why would one do so
> (i.e. what is lacking in t
Hi Sage-devel,
The talks linked to below are very interesting. In particular,
see the talk by Paul Zimmerman (the MPFR guy) for a history of
pari with lots of pictures.
William
-- Forwarded message --
From: Bill Allombert <[EMAIL PROTECTED]>
Date: Oct 30, 2007 3:22 PM
Subject:
I agree about not rewriting for the sake of it -- but this was on the
to-do list for SD5, wasn't it? Perhaps the to-do is to implement over
GF(q) what we already have over GF(p).
John (forwarding to sage-devel a thread that started amongst SD6 planners)
-- Forwarded message --
On Oct 30, 2007, at 1:11 PM, Carl Witty wrote:
> On Tue, 2007-10-30 at 11:24 -0700, Robert Bradshaw wrote:
>> I don't see this one--could you send me a link?
>>
>> I didn't know we used SAGE objects in any numpy classes.
>
> Numpy provides a type of matrices of arbitrary Python objects.
>
> http:
On Oct 30, 11:03 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On 10/30/07, Paul Zimmermann <[EMAIL PROTECTED]> wrote:
> > 27510639 1080 -rw-rw-r-- 1 zimmerma spaces1098688 Oct 30 11:23
> > /local/spaces/logiciels/sage-2.8.10/p4/sage/devel/sage-main/build/temp.linux-i686-2.5/sage/schemes
On Tue, Oct 30, 2007 at 10:48:47AM -0700, William Stein wrote:
> > Anyhow, I guess my rock bottom question is whether this design restraint
> > could
> > be reconsidered? I'd be much happier to see some concrete systems that it
> > breaks that we need (and mathematica doesn't count in my mind si
On 10/30/07, Paul Zimmermann <[EMAIL PROTECTED]> wrote:
> I wonder about the size of the SAGE installation. I just compiled sage-2.8.10
> on my computer and did:
>
> mermoz% make install DESTDIR=/local/spaces/logiciels/sage-2.8.10/p4
>
> which uses more than 1Gb of memory:
>
> mermoz% du -s /loca
On 10/30/07, Joel B. Mohler <[EMAIL PROTECTED]> wrote:
> I tried to break the singular interface with an '_' in my patched version and
> could not do so. It also seems that the singular language itself allows
> underscores. I realize that the argument isn't so much about singular as
> some langu
On Mon, Oct 29, 2007 at 02:00:18PM -0700, William Stein wrote:
> On 10/29/07, Joel B. Mohler <[EMAIL PROTECTED]> wrote:
> > sage: P.=ZZ[[]]
> > sage: latex(P)
> > \mathbf{Z}[[\alpha_{15}]]
> >
> > sage: P,alpha_beta12=PolynomialRing(ZZ,'alpha_beta12').objgen()
> > sage: latex(alpha_beta12)
> > \al
> just link the new spkg from ticket #971, I will start on the 2.8.11
> release cycle late on Wednesday. Hopefully we can sort it all out by
> the release planned for this Friday.
I don't have access to the tracker, but here is how you can generate
the sympy spkg:
hg clone http://hgsympy.hopto.o
18 matches
Mail list logo
