On Sun, Feb 15, 2009 at 3:33 PM, Ondrej Certik wrote:
>
> On Wed, Feb 11, 2009 at 7:13 PM, Nick Alexander wrote:
>>
>>> Indeed, it was a oneliner:
>>>
>>> diff -r b0aa7ef45b3c sage/server/notebook/user_conf.py
>>> --- a/sage/server/notebook/user_conf.py Mon Jan 05 23:03:45 2009 -0800
>>> ++
On Feb 15, 10:31 am, William Stein wrote:
> On Sat, Feb 14, 2009 at 7:45 AM, mabshoff wrote:
> The Fedora 64-bit segfaults issue is one of these. I just searched
> and couldn't find any tickets in trac about this, which is odd. I
> made some progress on that, in particular I found a work
On Feb 15, 12:53 pm, kcrisman wrote:
> I suspect if this is available people will take advantage of it. Many
> of us have perfectly serviceable computers which can't handle/can't
> afford the upgrade. I would just build from source as a dev wannabe,
> but having this available for platform
On Feb 15, 11:33 am, "Georg S. Weber"
wrote:
> Hi,
Hi Georg,
> maybe off-topic, I deem it on-topic here:
>
> Probably I will use OS X 10.4.11 for quite some more time, and I build
> Sage rather often for testing, and/or for my own personal use. Would
> it help if I provided, say, the OS X 10.
On Feb 15, 11:26 am, "Georg S. Weber"
wrote:
> Hi Mark,
> hi Michael,
> But e.g. for Mac OS X app bundles, it should be safe to call the "sage-
> location" script each and every time at the startup of Sage --- the
> additional time needed is negligible in the "good" case, and extremely
> wel
On Wed, Feb 11, 2009 at 7:13 PM, Nick Alexander wrote:
>
>> Indeed, it was a oneliner:
>>
>> diff -r b0aa7ef45b3c sage/server/notebook/user_conf.py
>> --- a/sage/server/notebook/user_conf.py Mon Jan 05 23:03:45 2009 -0800
>> +++ b/sage/server/notebook/user_conf.py Wed Feb 11 08:58:59
Pat LeSmithe wrote:
>
[...]
>
> Anyway, thanks for any interest, comments, and ideas!
>
This is now in:
http://trac.sagemath.org/sage_trac/ticket/5279
Jaap
> Sincerely,
> Pat LeSmithe
>
>
> >
>
--~--~-~--~~~---~--~~
To post to this group, send email
>
> Probably I will use OS X 10.4.11 for quite some more time, and I build
> Sage rather often for testing, and/or for my own personal use. Would
> it help if I provided, say, the OS X 10.4 .dmg files (Intel Core2Duo
> regularly and sometimes even PPC G4)? My time and my Internet upload
> connect
The MPIR project is pleased to announce their first release 0.9.0.
MPIR is based on the GMP project (specifically version 4.2.1 of GMP,
which was licensed LGPL v2+).
The main MPIR website is here:
http://www.mpir.org/
A source tarball is available here:
http://www.mpir.org/mpir-0.9.0.tar.gz
Hi,
maybe off-topic, I deem it on-topic here:
Probably I will use OS X 10.4.11 for quite some more time, and I build
Sage rather often for testing, and/or for my own personal use. Would
it help if I provided, say, the OS X 10.4 .dmg files (Intel Core2Duo
regularly and sometimes even PPC G4)? My
Hi Mark,
hi Michael,
actually I am using Mac OS X 10.4.11 on the Intel Core2Duo MacBook
where I tested it. I should have noted that I did download the source
distribution .tar and did build on this box my own "10.4" .dmg with
which I tested the new version of the script. (Aha -- I did rename the
On Sat, Feb 14, 2009 at 7:45 AM, mabshoff wrote:
>
> Hello folks,
>
> we are deep into the final stage of the 3.3 release and at this point
> there are various things you can do to help out:
>
> * review patches - this is the most important thing since there are
> plenty of things sitting in tra
On Feb 15, 6:46 am, mark mcclure wrote:
> On Feb 15, 4:59 am, "Georg S. Weber"
> wrote:
Hi Mark,
> > a patch is up for review at #5254.
>
> George,
>
> I applied your patch without success on my laptop at home.
> However, the problem could very well be that I've got OS
> 10.4.11 at home whil
On Feb 15, 4:59 am, "Georg S. Weber"
wrote:
> a patch is up for review at #5254.
George,
I applied your patch without success on my laptop at home.
However, the problem could very well be that I've got OS
10.4.11 at home while Michael built Sage.app for 10.5. I
can try it on 10.5 tomorrow at w
On Feb 13, 1:06 pm, ThePriest wrote:
Hi,
> So I found an easy exemple:
>
> Script.py contains:
>
> def f(n):
> return n*n
> _
>
> D=dsage.start_all()
>
> from Script import *
>
> R=D.eval_function(f,((4,{}), job_name='square')
>
> This give me the exact same error, what should I d
On Sun, Feb 15, 2009 at 1:25 AM, Sirius wrote:
>
> Hi everyone!
>
...
> The Inkscape SVG file with all my work on sage logos is downloadable
> from my GNOME Live homepage @ http://live.gnome.org/SirioBola%C3%B1os,
> and is available under a CC BY-NC-SA 2.5 MX License, with my express
> permissi
On 13 Feb., 11:34, mabshoff wrote:
> Ok, I figured it out. After downloading the dmg I dragged it to my
> desktop and double clicked on it to start. It came up, but Maxima/
> clisp did not start.
>
> So, after quitting I run that sage on the command line and low and
> behold the rebase script r
On 13 Feb., 11:34, mabshoff wrote:
> Ok, I figured it out. After downloading the dmg I dragged it to my
> desktop and double clicked on it to start. It came up, but Maxima/
> clisp did not start.
>
> So, after quitting I run that sage on the command line and low and
> behold the rebase script r
18 matches
Mail list logo
