#9976: Decorated functions/methods have generic signature in documentation
--------------------------------+-------------------------------------------
Reporter: jsrn | Owner: jsrn
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.7
Component: documentation | Keywords: sphinx, documentation, cython
inspection
Author: jsrn, Simon King | Upstream: N/A
Reviewer: Simon King | Merged:
Work_issues: |
--------------------------------+-------------------------------------------
Comment(by jsrn):
Replying to [comment:141 SimonKing]:
> Replying to [comment:140 jsrn]:
> Is timing really an issue for building the documentation?
It takes me about ½ hour to build the documentation; it would very be nice
if this at least didn't get worse...
>
> Also, I doubt that it will have a dramatic effect. After all, it just
means to compare two strings for any callable class instance that happens
to live on module level. It seems to me that such things do not occur very
often.
Ah, I had mixed up _sage_getdoc and _sage_getargspec -- as the latter
sometimes parses the entire source code and builds an AST to go over,
calls to this should not be too abundant. Indeed, the worst
_sage_getdoc_unformatted seems to do is convert the string to unicode;
this should not be very visible on timings.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9976#comment:142>
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 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.
