[sage-devel] Re: doctest coverage to 75%

2009-04-13 Thread Nicolas M. Thiery
On Thu, Apr 09, 2009 at 07:06:01PM -0700, William Stein wrote: > > 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% coverag

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread William Stein
On Fri, Apr 10, 2009 at 2:10 PM, mabshoff wrote: > > FYI: I have started a wiki page at > >   http://wiki.sagemath.org/doc4 We will start at 9am tomorrow morning. Latecomers and earlycomers welcome too. Everyone welcome. Login to sage.math.washington.edu with ssh Run irssi /server irc.freeno

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread mabshoff
FYI: I have started a wiki page at http://wiki.sagemath.org/doc4 If you are working on any coverage at the moment and/or have any relevant tickets please add them there so we avoid duplication of work. Re p-adics: It would be nice if the doctesting issues at #5499 could be resolved so that p

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread John Cremona
2009/4/10 Robert Bradshaw : > > On Apr 10, 2009, at 10:08 AM, William Stein wrote: > >> On Fri, Apr 10, 2009 at 9:51 AM, David Roe >> wrote: >>> >>> >>> On Fri, Apr 10, 2009 at 11:40 AM, John Cremona >>> >>> wrote: >>> :-)  There's a patch in trac (#4637) adding documentation to p- >>>

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread Robert Bradshaw
On Apr 10, 2009, at 10:08 AM, William Stein wrote: > On Fri, Apr 10, 2009 at 9:51 AM, David Roe > wrote: >> >> >> On Fri, Apr 10, 2009 at 11:40 AM, John Cremona >> >> wrote: >>> >>> >> :-) There's a patch in trac (#4637) adding documentation to p- >> adics, and >> I'm going to write a bun

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread William Stein
On Fri, Apr 10, 2009 at 9:51 AM, David Roe wrote: > > > On Fri, Apr 10, 2009 at 11:40 AM, John Cremona > wrote: >> >> 2009/4/10 William Stein : >> > >> > On Fri, Apr 10, 2009 at 7:43 AM, John Cremona >> > wrote: >> >> >> >> 2009/4/10 William Stein : >> >>> >> >>> On Fri, Apr 10, 2009 at 3:09 AM

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread David Roe
On Fri, Apr 10, 2009 at 11:40 AM, John Cremona wrote: > > 2009/4/10 William Stein : > > > > On Fri, Apr 10, 2009 at 7:43 AM, John Cremona > wrote: > >> > >> 2009/4/10 William Stein : > >>> > >>> On Fri, Apr 10, 2009 at 3:09 AM, John Cremona > wrote: > > For me the trouble with extended

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread John Cremona
2009/4/10 William Stein : > > On Fri, Apr 10, 2009 at 7:43 AM, John Cremona wrote: >> >> 2009/4/10 William Stein : >>> >>> On Fri, Apr 10, 2009 at 3:09 AM, John Cremona >>> wrote: For me the trouble with extended_*.py is that I have no idea what they aactually are, so it is hard

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread William Stein
On Fri, Apr 10, 2009 at 7:43 AM, John Cremona wrote: > > 2009/4/10 William Stein : >> >> On Fri, Apr 10, 2009 at 3:09 AM, John Cremona wrote: >>> >>> For me the trouble with extended_*.py is that I have no idea what they >>> aactually are, so it is hard to get started >> >> But aren't you ju

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread John Cremona
2009/4/10 William Stein : > > On Fri, Apr 10, 2009 at 3:09 AM, John Cremona wrote: >> >> For me the trouble with extended_*.py is that I have no idea what they >> aactually are, so it is hard to get started > > But aren't you just dying to find out what they are? :-) Well... I did not even

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread William Stein
On Fri, Apr 10, 2009 at 3:09 AM, John Cremona wrote: > > For me the trouble with extended_*.py is that I have no idea what they > aactually are, so it is hard to get started But aren't you just dying to find out what they are? :-) William --~--~-~--~~~---~--~---

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread David Roe
I can work on that tomorrow, in addition to p-adics. David On Fri, Apr 10, 2009 at 1:38 AM, William Stein wrote: > > 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 n

[sage-devel] Re: doctest coverage to 75%

2009-04-10 Thread John Cremona
For me the trouble with extended_*.py is that I have no idea what they aactually are, so it is hard to get started John 2009/4/10 William Stein : > > 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 ge

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread William Stein
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*

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread Alex Ghitza
> > 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

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread William Stein
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 --

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread mabshoff
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

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread William Stein
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

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread davidloeffler
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

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread Jason Grout
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

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread David Roe
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

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread Robert Bradshaw
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

[sage-devel] Re: doctest coverage to 75%

2009-04-09 Thread John Cremona
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