On Wednesday, March 20, 2013 5:09:40 AM UTC, Nils Bruin wrote: > On Mar 19, 9:10 pm, Robert Bradshaw <rober...@math.washington.edu> > wrote: > > Sounds good. What if we called this foo.uncached(args) instead (which > > is more verbose but much clearer, and tab completion shouldn't make > > that too bad...) I could make cached methods work as well. > > Do we actually have a use-case? >
I had to use it in the conjugacy classes module in the ConjugacyClassGAP.set() method, which is a cached method that sometimes needs to delegate to the (also cached) ConjugacyClass.set() if there is a problem converting a GAP group elements back into sage (which is what happens at the moment with elements of some matrix groups). Since a cached method cannot call another cached method, I needed to access the uncached version directly. I can dig-up the discussion at sage devel if that would help. Cheers, J -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
