#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:6 jdemeyer]:
> The question is also: if there is a method
> {{{
> def f(self, arg=1)
> }}}
> do we require that `obj.f()` and `obj.f(1)` and `obj.f(arg=1)` all use
the same cache entry? If you don't require that, there might be a solution
by working on the level of `*args` and `**kwds`.
Yes, we do require that. Equivalent inputs should result in identical
output.
The problem occurs when the cached method is bound to an instance. At that
point, we want to know if the method accepts ''any'' argument in addition
to `self`. If it does, then a `CachedMethodCaller` is set as an attribute
of the instance. If it does not, then a `CachedMethodCallerNoArgs` is
bound to the method. If sage can't answer the question, then an
`AttributeError` is raised. We don't need to know all argument names and
all defaults, but we do need to know their number.
--
Ticket URL: <http://trac.sagemath.org/ticket/17814#comment:7>
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.
