#12978: conditionally_defined decorator for methods and other attributes
-------------------------------------------------+-------------------------
       Reporter:  nthiery                        |        Owner:  jason
           Type:  enhancement                    |       Status:  new
       Priority:  major                          |    Milestone:  sage-
      Component:  misc                           |  wishlist
       Keywords:  categories,                    |   Resolution:
  conditionally_defined                          |    Merged in:
        Authors:                                 |    Reviewers:
Report Upstream:  N/A                            |  Work issues:
         Branch:                                 |       Commit:
   Dependencies:  #15056                         |     Stopgaps:
-------------------------------------------------+-------------------------

Comment (by nthiery):

 Replying to [comment:18 SimonKing]:
 > > At some point, I need to find out what class the default
 > > implementation is defined for, so that one can get the non-default
 > > implementation by a call to `super`. That's a problem. Currently,
 > > I go up the class hierarchy and test whether the
 > > conditionally_defined instance is in the `__dict__` of the
 > > class. But if the conditionally_defined instance is wrapped in a
 > > different wrapper (e.g., a cached_method), then this way of
 > > determining the class will fail.

 I haven't looked at the code; just wondering: since ``lazy_attribute``
 is already doing something like this could this piece of work be
 delegated to it?

 > PS: In my current patch, I trust that the class that Python gives as
 > an argument to `__get__` is the class in which the
 > object-to-be-bound is found. It seems to work.

 The Descriptor protocol is described quite in detail in
 http://docs.python.org/2/howto/descriptor.html; maybe it says
 something about this.


 By the way: the
 {{{
     @cached_method
     @conditionally_method
     ...
 }}}
 feature is nice looking for comprehensiveness, but I am really not
 sure I have a real use case for it. So if dropping this feature makes
 the code simpler, go for it.

 Cheers,
                           Nicolas

--
Ticket URL: <http://trac.sagemath.org/ticket/12978#comment:20>
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/groups/opt_out.

Reply via email to