On 9/7/10 11:06 PM, robertwb wrote:
On Sep 6, 9:19 pm, Jason Grout wrote:
On 9/6/10 10:59 PM, William wrote:
Jason,
Could you change the code in fast_callable? Clearly if something is
not hashable then it is not a dictionary key.
Yes, that was what I tried first. Then I was really puzz
On Sep 6, 9:19 pm, Jason Grout wrote:
> On 9/6/10 10:59 PM, William wrote:
>
> > Jason,
>
> > Could you change the code in fast_callable? Clearly if something is
> > not hashable then it is not a dictionary key.
>
> Yes, that was what I tried first. Then I was really puzzled why the
> function w
Hi,
As Kevin pointed out in his reply, there are guidelines and policies for
including new code, described in the Developer Guide (which starts with
a very nice walk-through). It's quite a bit to do though, so if you
want to start small or get others interested to help, you can open a new
ticket
"How to contribute to Sage"
http://sagemath.org/development.html
As I understand it, all additions to Sage are made through the trac
server at http://trac.sagemath.org/sage_trac/. You need to obtain a
trac account. You do not contribute to Sage by providing new code-you
provide a patch through t
On 09/07/2010 06:03 PM, Dr. David Kirkby wrote:
> I decided to run "sage -upgrade" today - for about the first time ever.
> I'm going to try to upgrade sage-4.5.3.alpha2 to sage-4.5.3. I don't
> know if its a good idea to update alphas or not, but I'm not bothered if
> it fails or not.
>
>
> I ge
I decided to run "sage -upgrade" today - for about the first time ever. I'm
going to try to upgrade sage-4.5.3.alpha2 to sage-4.5.3. I don't know if its a
good idea to update alphas or not, but I'm not bothered if it fails or not.
I get this:
Testing mirrors...
[2 ] boxen.math.washington
On 09/ 7/10 02:57 PM, Jason Grout wrote:
On 9/7/10 5:55 AM, Dr. David Kirkby wrote:
[snip]
Do we have any guidelines on these sorts of issues?
If not, I'd propose that any changes outside the original scope of the
ticket that will take the author less than 30 minutes to address, would
be qu
On 9/7/10 2:35 PM, Bill Hart wrote:
Hi all,
After really a lot of people from Sage related projects and elsewhere wrote to
me and said they'd support a BSD licensed bignum library, I finally decided to
go ahead with creating such a library.
Could you comment on the relationship of this with G
Sorry I mean that I want this algorithm to come in next sage versions!
On Sep 7, 11:45 pm, Tom Boothby wrote:
> Publish it onhttp://sagenb.organd email it to your friends!
>
>
>
> On Tue, Sep 7, 2010 at 12:36 PM, Ehsan wrote:
> > Dear All
> > I have used sage to implement and test an algorithm r
Publish it on http://sagenb.org and email it to your friends!
On Tue, Sep 7, 2010 at 12:36 PM, Ehsan wrote:
> Dear All
> I have used sage to implement and test an algorithm related to
> discrete math. Now I like to share it by others. what's the simplest
> way to do so?
> Thank you for your helps
Dear All
I have used sage to implement and test an algorithm related to
discrete math. Now I like to share it by others. what's the simplest
way to do so?
Thank you for your helps :)
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an ema
Hi all,
After really a lot of people from Sage related projects and elsewhere wrote to
me and said they'd support a BSD licensed bignum library, I finally decided to
go ahead with creating such a library.
The most recent request came from Paul Davey of the Falcon language project:
http://www.fal
On 9/7/10 5:55 AM, Dr. David Kirkby wrote:
[snip]
Do we have any guidelines on these sorts of issues?
If not, I'd propose that any changes outside the original scope of the
ticket that will take the author less than 30 minutes to address, would
be quite reasonable.
But if the changes are go
This is now trac ticket 9867.
Please review!
On Sep 7, 8:56 pm, Dima Pasechnik wrote:
> I've
> madehttp://boxen.math.washington.edu/home/dima/packages/gap-4.4.12.p5.spkg
> with the proper patches, bells, etc., and
> will make a ticket to update the things shortly.
>
> On Sep 7, 8:14 pm, Dima Pas
On Sep 7, 8:02 am, Nathann Cohen wrote:
> Sorry to answer to such an exhaustively documented message with a
> simple line David, but I honestly think that beginning to write down
> rules about how Sage developpers should deal with each other is the
> end of natural/good mood/pleasure in particip
I've made
http://boxen.math.washington.edu/home/dima/packages/gap-4.4.12.p5.spkg
with the proper patches, bells, etc., and
will make a ticket to update the things shortly.
On Sep 7, 8:14 pm, Dima Pasechnik wrote:
> Hi Simon, hi all,
>
> I've made a small patch to GAP that fixes the problem.
> (in
Hi Simon, hi all,
I've made a small patch to GAP that fixes the problem.
(inspired by the corresponding Sage Python code :))
With this patch I get on Sparc:
sage: gap_console()
GAP4, Version: 4.4.12 of 17-Dec-2008, sparc-sun-solaris2.10-gcc
gap> Reset(GlobalMersenneTwister);; List([1..10],i->Rand
Sorry to answer to such an exhaustively documented message with a
simple line David, but I honestly think that beginning to write down
rules about how Sage developpers should deal with each other is the
end of natural/good mood/pleasure in participating
It's a bit like life... You work with ma
Leif Leonhardy has done a *huge* amount to improve the quality of Sage. I think
if more authors and reviewers were like Leif, we would not have many of the
quality control issues we have in Sage today.
I personally think it is quite reasonable to suggest an author make some changes
to a packag
Hello sage-devel,
As far as we know, there are no more remaining issues for the PARI
update (#9343). We haven't had any doctest failures for a while now.
The main issues recently have been with PARI not compiling properly on
various machines, but all those seem to be fixed now.
I have made a com
On 09/ 7/10 09:59 AM, Nicolas M. Thiery wrote:
On Wed, Aug 25, 2010 at 05:13:26PM +0100, Dr. David Kirkby wrote:
So, if no one seems to care, does this mean that this is implicitly
generally accepted as an optional package?
Vote:
[ ] Yes! Include dot2tex
[ ] No!
Cheers,
On Wed, Aug 25, 2010 at 05:13:26PM +0100, Dr. David Kirkby wrote:
> >So, if no one seems to care, does this mean that this is implicitly
> >generally accepted as an optional package?
> >
> >Vote:
> > [ ] Yes! Include dot2tex
> > [ ] No!
> >
> >Cheers,
> > Nicolas
> >--
Hi Mike!
On 7 Sep., 10:42, Simon King wrote:
> ...
> That's VERY cool!
... modulo one critical comment: In principal (although it should
rarely occur in "real life") one can have several instances of an
interface. So, I think that current_randstate().set_seed_gap() should
accept an optional argu
On 09/ 7/10 08:20 AM, Mitesh Patel wrote:
On 08/24/2010 08:01 PM, William Stein wrote:
On Tue, Aug 24, 2010 at 1:38 PM, William Stein wrote:
On Mon, Aug 23, 2010 at 8:25 PM, Jonathan Hanke wrote:
Hi,
I'm trying to build sage 4.5.2 on a Sun Fire X4450 server (Intel Xenon
processors) running
Hi Mike!
On 7 Sep., 01:05, Mike Hansen wrote:
> On Mon, Sep 6, 2010 at 3:56 PM, Simon King wrote:
> > So indeed, it is not "Solaris vs. non-Solaris" but "little vs. big
> > endian", as the GAP people suspected.
>
> This is what I said in my first response and can be taken care of with
> current_
Minh Nguyen gets the error below on a GCC compile farm Debian 5.0
machine (gcc100.fsffrance.org, AMD Opteron(tm) Processor 252 @ 2647.708
MHz). Please see
http://trac.sagemath.org/sage_trac/ticket/9866
sage -t -long "devel/sage/sage/schemes/elliptic_curves/heegner.py"
Exception RuntimeError: R
On 08/24/2010 08:01 PM, William Stein wrote:
> On Tue, Aug 24, 2010 at 1:38 PM, William Stein wrote:
>> On Mon, Aug 23, 2010 at 8:25 PM, Jonathan Hanke wrote:
>>> Hi,
>>>
>>> I'm trying to build sage 4.5.2 on a Sun Fire X4450 server (Intel Xenon
>>> processors) running Redhat linux (Enterprise ed
27 matches
Mail list logo
