#4588: [with patch; needs review] doctest -- get rid of the "feature" where
docstrings with require, optional, and package all in them are
automatically marked optional
---------------------+------------------------------------------------------
 Reporter:  was      |        Owner:  mabshoff
     Type:  defect   |       Status:  new     
 Priority:  major    |    Milestone:  sage-3.3
Component:  doctest  |   Resolution:          
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by was):

  * summary:  [with patch; not ready for review] doctest -- get rid of the
              "feature" where docstrings with require,
              optional, and package all in them are
              automatically marked optional => [with patch;
              needs review] doctest -- get rid of the
              "feature" where docstrings with require,
              optional, and package all in them are
              automatically marked optional

Comment:

 The attached sage patches fix all missing # optionals after applying the
 scripts patch (the first one -- trac_4588-scripts.patch).  I also greatly
 improve the use of
 {{{
   # optional -- name_of_package
 }}}
 while I was at it.

 However, note that this revealed some bugs in David Joyner's
 linear_code.py stuff.  See #5067. Thus I believe this patch should receive
 a positive review *despite* that after applying it suddenly four doctests
 will fail.   I've made #5067 a blocker.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4588#comment:3>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to