[sage-devel] Re: Inheriting from a Matrix class?

2007-06-20 Thread Jason Grout
[EMAIL PROTECTED] wrote: > Hi All, > > I am trying to write a small class which implements symmetric > matrices, but I'm unclear how to inherit from > sage.matrix.matrix_dense. How can I tell what the initialization > does, and how to properly call it? I tried looking at > sage.matrix.matrix_in

[sage-devel] Re: spkg for sage_c_lib

2007-06-20 Thread didier deshommes
On 6/20/07, Joel B. Mohler <[EMAIL PROTECTED]> wrote: > Anyhow, the new package for sage_c_lib gets a bit confusing because we had a > mercurial repository for the actual development of the sage_c_lib in the > original sage_c_lib spkg. The new spkg spec calls for a mercurial repository > for the

[sage-devel] C++ object construction/destruction

2007-06-20 Thread Joel B. Mohler
Here's a bit of a trick which I think might be of interest to people who wish to use C++ from pyrex. I apologize to the pyrex list if this is already amply covered (I was unable to find searchable mailing list archives to search for my possible redundancy.) Here's the situation. I have a C++

[sage-devel] Re: spkg for sage_c_lib

2007-06-20 Thread Joel B. Mohler
On Wednesday 20 June 2007 08:33, Joel B. Mohler wrote: > Here's some options for the purposes of voting on what should happen for > the sage_c_lib.spkg: > 1) Have a mercurial repository in the root of the spkg for the spkg > scripts and a *seperate* mercurial repository for development of the act

[sage-devel] spkg for sage_c_lib

2007-06-20 Thread Joel B. Mohler
Didier has posted a repackaged sage_c_lib (either off-list or on-list -- I forget) which adheres to the new spkg format. This mail is follow-up to that to more formally inquire about how to proceed for the sage_c_lib. I must say that I like this new format very much. It's much clearer what i

[sage-devel] Re: Small Scale AES Variants

2007-06-20 Thread Martin Albrecht
> I got them both, and I will have a look tonight. Does this version contain > the bugfix you gave me in IRC about 3 weeks ago? I am not remembering too > much about the details at the moment and I do not have my changelog around > since I am travelling. No, because that one applied to the CTC ge

[sage-devel] Re: Small Scale AES Variants

2007-06-20 Thread Michael Abshoff
Martin Albrecht wrote: > >> Slightly OT: Do you plan to release the Small Scale AES with you >> mutlivariate crypto system package any time soon? I have some code to >> create SymbolicData.org output for the CTC examples (which still needs >> to be cleaned up). I am currently at CoCoA School and n

[sage-devel] Re: Subject : THE FEEL GOOD FACTOR!

2007-06-20 Thread David Joyner
Actually, that's what I assumed "recent" meant! I didn't see the options phrased the way you have it. The other choice is to moderate everything. The good news is that I've already had on junk mail show up for moderation, so it is working. +++ On 6/20/07, kaimmel

[sage-devel] Small Scale AES Variants

2007-06-20 Thread Martin Albrecht
> Slightly OT: Do you plan to release the Small Scale AES with you > mutlivariate crypto system package any time soon? I have some code to > create SymbolicData.org output for the CTC examples (which still needs > to be cleaned up). I am currently at CoCoA School and next week is > MEGA, so I won'

[sage-devel] Very subtle bug in ... pyrex???

2007-06-20 Thread Gonzalo Tornaria
This was driving me crazy... There is either a bug or a very subtle difference in exception semantics between python and pyrex. This is demonstrated by the following python code: - try: raise TypeError except TypeError: print "A" QQ.has_coerce_map_from(ZZ) print "