On Thu, Apr 9, 2009 at 7:41 PM, Alex Ghitza wrote:
>
>>
>> We will have a docday this Saturday, with the insanely ambitious goal
>> of getting to 70%. This is probably not humanely possible for a
>> single person to do in 8 hours, so I hope I'm not the only one (I
>> estimate it takes *at least*
I, for one, am not interested in supporting a browser which is
unpopular, buggy, and still in beta. Keep an eye on? Sure. Fix?
Probably not -- we've uncovered a couple of Firefox bugs with the
notebook. From the deepest depth of my humility, in my most
insignificant of unworthy opinions, the C
>
> We will have a docday this Saturday, with the insanely ambitious goal
> of getting to 70%. This is probably not humanely possible for a
> single person to do in 8 hours, so I hope I'm not the only one (I
> estimate it takes *at least* 3 minutes per doctest, which comes to
> 37.8 hours for 756
Hi,
WHERE DO WE STAND?
Here's the Sage doctest coverage status:
We need 296 more function to get to 68% coverage.
We need 756 more function to get to 70% coverage.
We need 1905 more function to get to 75% coverage.
We will have a docday this Saturday, with the insanely ambitious goal
of getti
On Thu, Apr 9, 2009 at 6:32 PM, mabshoff wrote:
>
>
>
> On Apr 9, 5:53 pm, William Stein wrote:
>> On Thu, Apr 9, 2009 at 11:13 AM, davidloeffler
>> wrote:
>
>
>
>> Great. I've refereed this (positively). You fixed *numerous* bugs in
>> the code, imho, when writing those 28 new doctests --
On Apr 9, 5:53 pm, William Stein wrote:
> On Thu, Apr 9, 2009 at 11:13 AM, davidloeffler
> wrote:
> Great. I've refereed this (positively). You fixed *numerous* bugs in
> the code, imho, when writing those 28 new doctests -- great work!
> Let's keep the doctest patches coming.
Yep, note
On Thu, Apr 9, 2009 at 11:13 AM, davidloeffler wrote:
>
>
>
> On Apr 9, 9:45 am, William Stein wrote:
>>
>> I hope those of you who feel qualified to write doctests, will help
>> out. It's nearly impossible for one person to do all 1900 of those
>> doctests in the next month. Writing doctests
On Apr 9, 9:28 pm, Jason Grout wrote:
> I've installed Chromium on Ubuntu (I think there's even a .deb for it).
>
there is no working native linux build of chrome or chromium. only
something very old for wine.
the branch for linux development has some sort of test gui, but it's
really not usea
Feeding the factors to Sage's factor command to check they are prime
is precisely what proof=true is all about. Testing primality in a
proven way, for numbers bigger than 10^16 is still very slow as there
is no really good algorithm known for it. I have some code written by
a student of mine (Pete
On Apr 9, 2:11 pm, mabshoff wrote:
> On Apr 9, 2:03 pm, Peter Jeremy wrote:
> The primality test for pari is known to be lead to false results up to
> 10^14 or so (FLINT's is up to 10^16 IIRC what Bill told me a couple
> days ago).
Opps, I don't know what I was thinking, but the above make
On Apr 9, 2:03 pm, Peter Jeremy wrote:
> On 2009-Apr-07 21:49:12 -0700, William Stein wrote:
>
>
>
> >On Tue, Apr 7, 2009 at 9:24 PM, Bill Hart
> >wrote:
> >> The reason it runs slow is a.factor() is bizarrely slow in Sage. It's
> >> like a factor of 50 times slower than Pari.
>
> >There are
On 2009-Apr-07 21:49:12 -0700, William Stein wrote:
>
>On Tue, Apr 7, 2009 at 9:24 PM, Bill Hart wrote:
>> The reason it runs slow is a.factor() is bizarrely slow in Sage. It's
>> like a factor of 50 times slower than Pari.
>
>There are some differences:
> (1) pari's factor is *not* provably c
On Apr 9, 12:53 pm, Chris Godsil wrote:
Hi Chris,
> I tried to compile sage-3.4 on a Mac Pro (two quad-core intel xeon
> processors, OS 10.5.6) using gcc4.0.1. As instructed, I hid /opt/
> local. Nonetheless I failed; what seems to be the relevant part of
> install.log is included below.
>
I tried to compile sage-3.4 on a Mac Pro (two quad-core intel xeon
processors, OS 10.5.6) using gcc4.0.1. As instructed, I hid /opt/
local. Nonetheless I failed; what seems to be the relevant part of
install.log is included below.
I have installed the binary version and it seems to run, althoug
On Apr 9, 12:28 pm, Jason Grout wrote:
> William Stein wrote:
> > Thanks for the heads up. Is all Chrome stuff still windows only?
>
> I've installed Chromium on Ubuntu (I think there's even a .deb for it).
> Chromium is the open-source project that Chrome is based on.
>
> http://code.goo
William Stein wrote:
> On Thu, Apr 9, 2009 at 5:37 AM, Harald Schilly
> wrote:
>> There is a report http://bit.ly/lwzy6 that Chrome 2 (the beta version
>> of googles browser, currently at version 1) has issues with javascript
>> and css on Sage's notebook page.
>> Someone should look into it and
On Apr 9, 2009, at 11:31 AM, mabshoff wrote:
> On Apr 9, 11:01 am, Ondrej Certik wrote:
>> On Thu, Apr 9, 2009 at 10:33 AM, Arnaud Bergeron
>> wrote:
>
>
>
>>> Or simply, to keep the existing simplicity, change %myhandler to
>>> call
>>> sage_myhandler and rename the existing ones. There
On Apr 9, 6:59 pm, William Stein wrote:
> I noticed another bug at the above url and reported it to trac:
>
> http://trac.sagemath.org/sage_trac/ticket/5726
thx, public bugtracker is clean again ;)
h
--~--~-~--~~~---~--~~
To post to this group, send email to sa
On Apr 9, 11:01 am, Ondrej Certik wrote:
> On Thu, Apr 9, 2009 at 10:33 AM, Arnaud Bergeron wrote:
> > Or simply, to keep the existing simplicity, change %myhandler to call
> > sage_myhandler and rename the existing ones. There is very little
> > probability of other projects using sage_ a
On Apr 9, 9:45 am, William Stein wrote:
>
> I hope those of you who feel qualified to write doctests, will help
> out. It's nearly impossible for one person to do all 1900 of those
> doctests in the next month. Writing doctests is not easy and it
> absolutely requires experience experience wi
On Thu, Apr 9, 2009 at 10:33 AM, Arnaud Bergeron wrote:
>
> 2009/4/7 Brian Granger :
>>
>>> That seems awfully complicated. How about (untested):
>>>
>>> sage_python = python
>>> from sympy import *
>>> python = sage_python
>>>
>>> or (even shorter, and still untested):
>>>
>>> from sympy import
Update:
I just downloaded and tried it out. Alfredo you are
completely right, this is exactly what we need!
I'll follow the steps in the forum to get the eth0 up
and working and try out the mkxpud to see how it
works.
This is really exciting. Thanks once again for sharing
your discovery!
Greeti
2009/4/7 Brian Granger :
>
>> That seems awfully complicated. How about (untested):
>>
>> sage_python = python
>> from sympy import *
>> python = sage_python
>>
>> or (even shorter, and still untested):
>>
>> from sympy import *
>> restore('python')
>
> Sure these may work, but in my mind they ar
Alfredo,
I'm downloading it right now. It's size is really amazing :)
I'll send some feedback in this week about how did it go.
Thanks!
Lucio.
On Wed, Apr 8, 2009 at 11:17 PM, Alfredo Portes wrote:
>
> Hi Lucio,
>
> I have not been able to test the image, sorry. I will try to test this
> week
On Thu, Apr 9, 2009 at 5:32 AM, Pat LeSmithe wrote:
>
> Please see the attached snapshots. The top and bottom bars also have a
> search box and source link.
>
> If there's interest, I can try to get the toggle working in live
> documentation. I'd greatly appreciate a critique of the JavaScript
On Thu, Apr 9, 2009 at 5:37 AM, Harald Schilly wrote:
>
> There is a report http://bit.ly/lwzy6 that Chrome 2 (the beta version
> of googles browser, currently at version 1) has issues with javascript
> and css on Sage's notebook page.
> Someone should look into it and keep an eye on it once Chro
On Thu, Apr 9, 2009 at 4:44 AM, Golam Mortuza Hossain
wrote:
>
> On Thu, Apr 9, 2009 at 8:18 AM, Carlo Hamalainen
> wrote:
>> but I get a doctest failure on calculus.py. The first time
>> I ran sage -testall I saw this:
>>
>>
>> sage -t "devel/sage/sage/calculus/calculus.py"
>> *** *** Error: T
David Roe wrote:
> On Thu, Apr 9, 2009 at 5:19 AM, Robert Bradshaw <
> rober...@math.washington.edu> wrote:
>
>> On Apr 9, 2009, at 1:49 AM, John Cremona wrote:
>>
>>> Can we at the same time convert more files to ReST and hence get them
>>> included in the Reference manual? Although that manual
William Stein wrote:
> On Wed, Apr 8, 2009 at 2:16 PM, William Stein wrote:
>> On Wed, Apr 8, 2009 at 2:11 PM, ahmet alper parker
>> wrote:
>>> Hello Everybody,
>>> Is there any document that compares Matlab, Mathematica and Sage (Plus all
>>> the contributing codes, in example Maxima, etc.) fu
Hello
I just want to make it official that Sage has a fan page on facebook.
I'm not sure in what direction this will go, but some viral marketing
shouldn't hurt Sage at all! There are already more than 200 fans after
less than 2 weeks since it is online. You can post messages about
Sage, post som
There is a report http://bit.ly/lwzy6 that Chrome 2 (the beta version
of googles browser, currently at version 1) has issues with javascript
and css on Sage's notebook page.
Someone should look into it and keep an eye on it once Chrome 2 is
released. Remember, Chrome has its own V8 javascript engi
On Thu, Apr 9, 2009 at 8:18 AM, Carlo Hamalainen
wrote:
> but I get a doctest failure on calculus.py. The first time
> I ran sage -testall I saw this:
>
>
> sage -t "devel/sage/sage/calculus/calculus.py"
> *** *** Error: TIMED OUT! PROCESS KILLED! *** ***
> *** *** Error: TIMED OUT! *** ***
> **
Hi,
I built 3.4.1.rc1 on my Asus EEE PC 1000H (Intel Atom). The previous
issue with gmp-mpir not compiling has been fixed (thanks to Bill Hart
and others) but I get a doctest failure on calculus.py. The first time
I ran sage -testall I saw this:
sage -t "devel/sage/sage/calculus/calculus.py"
*
On Thu, Apr 9, 2009 at 5:19 AM, Robert Bradshaw <
rober...@math.washington.edu> wrote:
>
> On Apr 9, 2009, at 1:49 AM, John Cremona wrote:
>
> > Can we at the same time convert more files to ReST and hence get them
> > included in the Reference manual? Although that manual is long, there
> > is a
On Apr 9, 2009, at 1:49 AM, John Cremona wrote:
> Can we at the same time convert more files to ReST and hence get them
> included in the Reference manual? Although that manual is long, there
> is a whole lot of stuff not mentioned in it, which is bad PR.
>
> What I mean in practice is, if someo
Can we at the same time convert more files to ReST and hence get them
included in the Reference manual? Although that manual is long, there
is a whole lot of stuff not mentioned in it, which is bad PR.
What I mean in practice is, if someone is going through a source file
whose doctests are incom
Hi,
In order to get Sage's doctest coverage to 75%, which is one of the
main goals for Sage-4.0, it is necessary to doctest about 1900
functions in the Sage library. I just did a test (see
http://trac.sagemath.org/sage_trac/ticket/5724 and
http://trac.sagemath.org/sage_trac/ticket/5725) and it
Dear all,
I encountered some mysterious problems earlier when I used .subs(locals
()), where some global variables such as pi and e were lost (see. e.g.
thread
http://groups.google.com/group/sage-support/browse_thread/thread/0f1086c43611242a?).
Now I found an example that demonstrates this a bi
38 matches
Mail list logo
