[sage-devel] Re: Evolution of the Overall Doctest Coverage of Sage since 3 years

> > PS : Can somebody indicate me how to stop the y-axis at 100 without > > losing the title ? > > Can you post your code? http://www.thales.math.uqam.ca/~labbes/Experimentations/coverage_evolution.py > One thought is that we really ought to use the matplotlib title > functionality.  From the gra

Re: [sage-devel] Evolution of the Overall Doctest Coverage of Sage since 3 years

That's not the trend I'd highlight in the code. Looks to me like we're overdue for a surge in doctest coverage. Can we get up to 95% in the next 3 releases? On Mon, Mar 7, 2011 at 5:42 PM, Sébastien Labbé wrote: > Hi, > > I just did a graph of the Evolution of the Overall Doctest Coverage of >

[sage-devel] Re: Evolution of the Overall Doctest Coverage of Sage since 3 years

On 3/7/11 7:42 PM, Sébastien Labbé wrote: PS : Can somebody indicate me how to stop the y-axis at 100 without losing the title ? Can you post your code? One thought is that we really ought to use the matplotlib title functionality. From the graph, it looks like Sage manually adds a text i

Re: [sage-devel] Re: exceptions, Python, Cython, C

That would do it :). This is why we need automatic .h -> .pxd declarations. Also, it's been thrown around a couple of times that it may be worth making "cdef foo()" a warning, forcing the user to explicitly declare "cdef object foo()" (or, in your case, "cdef int foo() :-). On Mon, Mar 7, 2011 at

[sage-devel] Re: exceptions, Python, Cython, C

The problem: I had a C function declared as "int foo()" but was importing it in Cython as "cdef foo()". Thus when foo returned 0, Cython thought this was a NULL pointer and raised the error above. Thanks for the help, everyone. -- To post to this group, send an email to sage-devel@googlegroups.c

Re: Fwd: [sage-devel] Re: Sage did not build on Fedora 13

Thanks. At home now. I'll check it tomorrow morning. Sincerely, Sazzad Bin Kamal -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.go

Re: Fwd: [sage-devel] Re: Sage did not build on Fedora 13

For the record, the real error is this: rm -f libatlas.so liblapack.so make -j1 libatlas.so liblapack.so libf77blas.so libcblas.so liblapack.so make[3]: Entering directory `/home/sazzad/sage-4.6.2/spkg/build/atlas-3.8.3.p17/ATLAS-build/lib' ld -melf_i386 -shared -soname libatlas.so -o libatlas.so

Re: [sage-devel] Re: Sage did not build on Fedora 13

Post full log. On Monday, March 7, 2011 3:46:36 AM UTC, SBK wrote: > > I've downloaded > atlas-3.8.3.p17.spkgand > copied it (after removing the older atlas spkg to a backup folder) > Now It says: > > Traceback (most recent call l

[sage-devel] Re: [sage-windows] Sage did not build on Fedora 13

On 03/ 6/11 12:52 PM, Sazzad wrote: This was my first try to build Sage on Fedora 13. It hanged after printing 'ATLAS build failed!'. By the way can anyone point me to Sage Cygwin port site?? I read on some thread, some times ago, where Prof. Stein the work is almost finished? I did read Cygwin