#17847: Cython: embed signatures in docstrings of Sage library code
-------------------------------------+-------------------------------------
       Reporter:  jdemeyer           |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-6.6
      Component:  cython             |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Jeroen Demeyer,    |    Reviewers:  Simon King, Jeroen
  Simon King                         |  Demeyer
Report Upstream:  Fixed upstream,    |  Work issues:
  but not in a stable release.       |       Commit:
         Branch:                     |  cced81b8c06b2eeb436c7876e5fed356e868e334
  u/SimonKing/ticket/17847           |     Stopgaps:
   Dependencies:                     |
-------------------------------------+-------------------------------------

Comment (by SimonKing):

 Replying to [comment:77 jdemeyer]:
 > Simon, I assume that "needs_review" implies that you agree with the
 commits on this branch that I made?

 That's why I inserted my name as a reviewer `:-)`

 But I must admit that I don't understand ''why'' your changes result in
 inserting the signature into the docstring. I just see that they ''do''.
 And I see that we can cope with it, and shall eventually be able to use
 the new information.

 So, perhaps you can explain how your changes really work, so that I'd
 really qualify as a reviewer...

--
Ticket URL: <http://trac.sagemath.org/ticket/17847#comment:78>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to