Here's the sparse matrix multiply function. There is lots of room for
optimization, and not only in using the unsafe get functions.
Robert
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, sen
On Fri, 03 Nov 2006 13:22:03 -0800, <[EMAIL PROTECTED]> wrote:
>
> pyrage
> sagerex
> sageX
> SAGeXtremelyFastExtensionLanguageScript
> hypersage
I actualy like "sageX" a lot. The "X" suggests speed.
But it also suggests "eXtension" code. And it is easy
to say and remember.
William
--~--~---
I think if you are really making a fork of pyrex, that non-SAGE users
might want to use (I think they most defenitely will as it has so many
improvements), you should name it something that
i) lets people know that it is useful outside of SAGE
ii) provides some indication of it origin
On 11/3/
pyrecs? pyreks?psyrex?(where the s is for SAGE).Of course this would mean that we would call pyrexc pyrecsc or pyreksc which is sort of incomprehensible. This also has the disadvantage of being a homonym with pyrex. I'm trying to think of a glassware-related pun that would be appropriate...
On 11/3
pyrage
sagerex
sageX
SAGeXtremelyFastExtensionLanguageScript
hypersage
On Fri, 3 Nov 2006, David Harvey wrote:
>
>
> On Nov 3, 2006, at 2:51 PM, William Stein wrote:
>
>> On Fri, 03 Nov 2006 11:42:29 -0800, alex clemesha <[EMAIL PROTECTED]>
>> wrote:
>>
>>> I vote for Spyrex too, not syrex ... t
On Nov 3, 2006, at 2:51 PM, William Stein wrote:
> On Fri, 03 Nov 2006 11:42:29 -0800, alex clemesha <[EMAIL PROTECTED]>
> wrote:
>
>> I vote for Spyrex too, not syrex ... that sounds like some medical
>> device :)
>
> Robert Bradshaw pointed out that Spyrex sounds like *spyware*! Also,
> when
Hmm ... SExtSo you're /really/ going to make a fork of Pyrex?
what about:PyrexS ( pronounced Pyrex - 'S', kinda like My-S-Q-L )or if you want less association with Pyrex, 'SAGext' is fine.-Alex
--~--~-~--~~~---~--~~
To post to this group, send email to sage-
On Fri, 03 Nov 2006 11:42:29 -0800, alex clemesha <[EMAIL PROTECTED]>
wrote:
> I vote for Spyrex too, not syrex ... that sounds like some medical
> device :)
Robert Bradshaw pointed out that Spyrex sounds like *spyware*! Also,
when I say "syrex", I might spit on somebody. Maybe an entirel
On Fri, 3 Nov 2006, William Stein wrote:
>
> On Fri, 03 Nov 2006 09:54:14 -0800, Robert Bradshaw
> <[EMAIL PROTECTED]> wrote:
>> I think the problem here is that it _assumes_ that x and y commute,
>> which is not the only option.
>>
>> I am still looking for a convincing reason that
>>
>> sa
On Fri, 03 Nov 2006 11:36:42 -0800, David Harvey
<[EMAIL PROTECTED]> wrote:
>
>
> On Nov 3, 2006, at 1:57 PM, William Stein wrote:
>
>> FYI -- I just made complete nicely documted Pyrex declarations for the
>> entire Python/C
>> API for SAGE (so nobody else do this). They'll be in the
>> deve
I vote for Spyrex too, not syrex ... that sounds like some medical device :)-AlexOn 11/3/06, David Harvey <
[EMAIL PROTECTED]> wrote:On Nov 3, 2006, at 1:57 PM, William Stein wrote:
> FYI -- I just made complete nicely documted Pyrex declarations for the> entire Python/C> API for SAGE (so nobody el
On Nov 3, 2006, at 1:57 PM, William Stein wrote:
> FYI -- I just made complete nicely documted Pyrex declarations for the
> entire Python/C
> API for SAGE (so nobody else do this). They'll be in the
> devel/sage/sage/ext subdirectory
> in the next release, and will make it easy to use any Pyth
On Nov 3, 2006, at 1:57 PM, William Stein wrote:
> Also, since I'm making so many changes to Pyrex, to avoid confusion (or
> making the
> Pyrex author angry) I'm going to call the SAGE branch of Pyrex by the
> name
> "Syrex",
> which means "SAGE Pyrex".
Surely you meant to say Spyrex.
Also, S
On Fri, 03 Nov 2006 10:53:46 -0800, Bill Page
<[EMAIL PROTECTED]> wrote:
>> (Or -- if anybody on sage-devel is interested in doing a SAGE
>> <--> REDUCE interface, let me know.)
>>
>
> Yes, I am interested. But of course I also have only limited
> time. I did a simple interface for Reduce on th
Hi,
FYI -- I just made complete nicely documted Pyrex declarations for the
entire Python/C
API for SAGE (so nobody else do this). They'll be in the
devel/sage/sage/ext subdirectory
in the next release, and will make it easy to use any Python/C API
function directly
from Pyrex.
Also, sin
On November 3, 2006 1:28 PM William Stein wrote:
>
> On Fri, 03 Nov 2006 07:58:07 -0800, Thomas Wolf wrote:
>
> > Hello William,
> >
> > Winfried Neun (ZIB Berlin) is with me and we work a lot on
> > porting REDUCE, fixing bugs,.. and wonder how the incorporation
> > of REDUCE under SAGE is goin
On Fri, 03 Nov 2006 09:54:14 -0800, Robert Bradshaw
<[EMAIL PROTECTED]> wrote:
> I think the problem here is that it _assumes_ that x and y commute,
> which is not the only option.
>
> I am still looking for a convincing reason that
>
> sage: (1/2) * Matrix(ZZ, 2, 2, [1,2,3,4])
>
> should n
On Fri, 03 Nov 2006 08:04:18 -0800, Joel B. Mohler
<[EMAIL PROTECTED]> wrote:
>
> On Fri, Nov 03, 2006 at 06:29:39AM -0800, William Stein wrote:
>>
>> On Fri, 03 Nov 2006 03:11:31 -0800, Joel B. Mohler
>> <[EMAIL PROTECTED]> wrote:
>>
>> >
>> > It appears that the python complex_number class wa
On Fri, 03 Nov 2006 07:58:07 -0800, Thomas Wolf <[EMAIL PROTECTED]> wrote:
> Hello William,
>
> Winfried Neun (ZIB Berlin) is with me and we work a lot on
> porting REDUCE, fixing bugs,.. and wonder how the incorporation
> of REDUCE under SAGE is going.
Unfortunately, I'm busy dealing with other
On Nov 3, 2006, at 8:39 AM, Bill Page wrote:
> On November 3, 2006 9:48 AM David Harvey wrote:
>>
>> On Nov 3, 2006, at 9:37 AM, Bill Page wrote:
>>
>>>
>>> Maybe it is interesting to consider how Axiom handles these
>>> coercions? For example:
>>>
>>> sage: x = axiom('x::MPOLY([x],INT)')
>>> sag
On November 3, 2006 9:48 AM David Harvey wrote:
>
> On Nov 3, 2006, at 9:37 AM, Bill Page wrote:
>
> >
> > Maybe it is interesting to consider how Axiom handles these
> > coercions? For example:
> >
> > sage: x = axiom('x::MPOLY([x],INT)')
> > sage: x.type()
> > MultivariatePolynomial([x],Intege
On Fri, Nov 03, 2006 at 06:29:39AM -0800, William Stein wrote:
>
> On Fri, 03 Nov 2006 03:11:31 -0800, Joel B. Mohler
> <[EMAIL PROTECTED]> wrote:
>
> >
> > It appears that the python complex_number class was moved to pyrex, but
> > then
> > the converted class was blithely ignored. Are the
On Fri, 03 Nov 2006 06:37:28 -0800, Bill Page
<[EMAIL PROTECTED]> wrote:
> On November 2, 2006 11:47 PM Robert Bradshaw wrote:
>> On Nov 2, 2006, at 8:28 PM, David Harvey wrote:
>> > On Nov 2, 2006, at 11:11 PM, Robert Bradshaw wrote:
> sage: x = axiom('x::MPOLY([x],INT)')
> sage: x.type()
> Mul
On Nov 3, 2006, at 9:37 AM, Bill Page wrote:
>
> Maybe it is interesting to consider how Axiom handles these
> coercions? For example:
>
> sage: x = axiom('x::MPOLY([x],INT)')
> sage: x.type()
> MultivariatePolynomial([x],Integer)
> sage: y = axiom('y::MPOLY([y],INT)')
> sage: y.type()
> Multiva
On November 2, 2006 11:47 PM Robert Bradshaw wrote:
>
> On Nov 2, 2006, at 8:28 PM, David Harvey wrote:
>
> > On Nov 2, 2006, at 11:11 PM, Robert Bradshaw wrote:
> >
> >>> This is much harder. I agree it would be nice, but how would you
> >>> handle something like
> >>>
> >>> sage: R. = ZZ["x"]
On Fri, 03 Nov 2006 04:05:13 -0800, David Harvey
<[EMAIL PROTECTED]> wrote:
> On Nov 3, 2006, at 12:08 AM, William Stein wrote:
>
>> Actually, I'm going to do this:
>>
>>SageObject
>>|
>>|
>> \|/
>> Parent
>>|
>>|
>> \|/
>> ParentWithGens
>>
>
On Fri, 03 Nov 2006 03:11:31 -0800, Joel B. Mohler
<[EMAIL PROTECTED]> wrote:
>
> It appears that the python complex_number class was moved to pyrex, but
> then
> the converted class was blithely ignored. Are they supposed to both
> still
> exist?
It's in transition. The pyrex class is i
On Nov 3, 2006, at 12:08 AM, William Stein wrote:
> Actually, I'm going to do this:
>
>SageObject
>|
>|
> \|/
> Parent
>|
>|
> \|/
> ParentWithGens
>
> Since the "Object" in ParentObject is redundant, and this is more
> consistent
> with "Elem
It appears that the python complex_number class was moved to pyrex, but then
the converted class was blithely ignored. Are they supposed to both still
exist?
--
Joel
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsub
On Thursday 02 November 2006 22:02, William Stein wrote:
> def _complex_mpfr_field_(self, CC):
> return make myself in CC.
>
> In sage/rings/complex_field.py you need to add code that calls
> _complex_mpfr_field_.
Good, I have started this. It bothers me just a bit that the analo
30 matches
Mail list logo
