#14017: Determine the correct argspec for python functions defined in cython
files
-------------------------+--------------------------------------------------
Reporter: SimonKing | Owner: jason
Type: defect | Status: new
Priority: major | Milestone: sage-5.7
Component: misc | Keywords: introspection cython argspec
Work issues: | Report Upstream: N/A
Reviewers: | Authors:
Merged in: | Dependencies:
Stopgaps: |
-------------------------+--------------------------------------------------
In the following simple example, sage_getargspec does not correctly
determine the arguments of a python function:
{{{
sage: cython("""
....: def f_cy(*args,**kwds):
....: pass
....: """)
sage: sage_getargspec(f_cy)
ArgSpec(args=['*args', '**kwds'], varargs=None, keywords=None,
defaults=None)
}}}
Writing the same in Python, one gets
{{{
sage: def f_py(*args,**kwds):
....: pass
....:
sage: sage_getargspec(f_py)
ArgSpec(args=[], varargs='args', keywords='kwds', defaults=None)
}}}
This bug is what currently prevents as to put `UniqueRepresentation` into
a cython file.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14017>
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].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
