On Monday, August 1, 2011 9:53:40 AM UTC-7, Michael Orlitzky wrote:
>
> On 07/26/11 15:31, Burcin Erocal wrote:
> >
> > It is a good start. Here are some suggestions:
> >
> > - The code blocks should be preceeded with :: and indented. More
> > information is available here:
> >
> > http://sa
On 07/26/11 15:31, Burcin Erocal wrote:
>
> It is a good start. Here are some suggestions:
>
> - The code blocks should be preceeded with :: and indented. More
> information is available here:
>
> http://sagemath.org/doc/developer/conventions.html#documentation-strings
I don't see the "::" do
On 07/26/11 15:31, Burcin Erocal wrote:
>>
>> How's this looking?
>
> It is a good start. Here are some suggestions:
>
> - The code blocks should be preceeded with :: and indented. More
> information is available here:
>
> http://sagemath.org/doc/developer/conventions.html#documentation-string
On Mon, 25 Jul 2011 12:20:35 -0400
Michael Orlitzky wrote:
> On 07/20/11 13:26, Burcin Erocal wrote:
> >
> > If you are adding tests only for integration, starting a new file
> > sage/symbolic/tests.py might be better.
> >
> > ...
> >
> > Don't forget to mention the ticket number in the test.
On 07/20/11 13:26, Burcin Erocal wrote:
>
> If you are adding tests only for integration, starting a new file
> sage/symbolic/tests.py might be better.
>
> ...
>
> Don't forget to mention the ticket number in the test.
>
How's this looking?
--
To post to this group, send an email to sage-dev
How about one adds a file with "bugs" in the name that lists the doctests
together with their _wrong_ output and corresponding trac link. That way,
we'll find out immediately which tickets are fixed by some upstream spkg
update...
--
To post to this group, send an email to sage-devel@googlegro
On 07/20/11 13:26, Burcin Erocal wrote:
> On Tue, 19 Jul 2011 14:44:10 -0400
> Michael Orlitzky wrote:
>
>> 2. Subject to #1, where is the most appropriate place to add the
>> tests? My first guess would be in the "TESTS:" section of
>> sage/calculus/calculus.py, but there appear to be some stand
On Tue, 19 Jul 2011 14:44:10 -0400
Michael Orlitzky wrote:
> 2. Subject to #1, where is the most appropriate place to add the
> tests? My first guess would be in the "TESTS:" section of
> sage/calculus/calculus.py, but there appear to be some standalone
> tests defined in sage/tests, too.
If you
I'm interested in adding unit tests for the open symbolics bugs
(particular the integrate ones that affect me most), and I was wondering,
1. Is this a good idea? Adding tests for open bugs means the test suite
will fail. There seem to exist two camps with differing opinions on this.
2. Subject to
