#17814: Make calling a cached method independent of source code inspection
--------------------------------+------------------------
Reporter: SimonKing | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.6
Component: distribution | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
--------------------------------+------------------------
Comment (by SimonKing):
Replying to [comment:8 jdemeyer]:
> The two statements below seem like a contraction: using the example
above, if you want to ensure that `obj.f()` and `obj.f(1)` and
`obj.f(arg=1)` use the same cache entry, you do need to know the names and
defaults of the arguments.
For ''calling'' the function, you of course need it (so, I admit that the
title of this ticket is misleading). However, for determining whether it
ought to be a `CachedMethodCaller` or a `CachedMethodCallerNoArgs`, it
suffices to know a little less.
And thank you for the link to `PyCFunction_GetFlags`. So, it seems that
`sage.misc.sageinspect` should get a little addition
`sage.misc.sage_inspect_cython` written in Cython that provides helpers
for inspection of Cython methods.
--
Ticket URL: <http://trac.sagemath.org/ticket/17814#comment:10>
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.
