#4813: [with patch, needs review] contribution to the tests/ directory
-------------------------+--------------------------------------------------
Reporter: ddrake | Owner: mabshoff
Type: enhancement | Status: new
Priority: minor | Milestone: sage-3.4
Component: doctest | Keywords:
-------------------------+--------------------------------------------------
From http://groups.google.com/group/sage-support/msg/3ea7ed2eeab0824a :
> Note that you could also submit a patch to Sage with the code you're
doctesting.
> I did that with all the tests from both of the books I published, and
> I encourage you and many others to do the same with the code from your
> article. The code would go in a file
>
> devel/sage/sage/tests/
>
> like the file devel/sage/sage/tests/book_stein_modform.py
>
> In fact, I could imagine having dozens of files in that directory, and
> when doctests break there, we could notify the authors before
> releasing the version of Sage that breaks their doctests for feedback
> -- then they could update their papers or Sage.
Here's the code from a preprint I just posted. I tried to follow
"official" style in writing the code -- comments about the style and so on
are welcome.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4813>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
