#7948: fix docstring processing errors in 4.3.1.rc0
-----------------------------+----------------------------------------------
Reporter: cremona | Owner: mvngu
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.3.1
Component: documentation | Keywords:
Work_issues: | Author:
Upstream: N/A | Reviewer:
Merged: |
-----------------------------+----------------------------------------------
Comment(by jhpalmieri):
I think that "obj is not a code object" arises for methods marked as
"lazy_attributes". These probably need to be dealt with in some special
way, but I don't know how to do it. Maybe it deserves its own ticket.
"Could not parse cython argspec" happens for several reasons. In lots of
cases, it's for functions with no arguments in cython files: {{{def
f():}}}. There is a mistake in sageinspect.py which causes such functions
to raise this error. I'm working on a patch. Actually, the code in
sageinspect.py for producing docstrings for cython functions, and in
particular for returning the list of arguments and their default values,
has some problems and ought to be rewritten. Again, maybe this belongs on
another ticket.
"arg is not a Python function": I don't know where this comes from.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7948#comment:3>
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.
