Hi Antonio, On 2015-02-19, Simon King <simon.k...@uni-jena.de> wrote: > On 2015-02-19, Antonio Rojas <aro...@archlinux.org> wrote: > I could try to make some experiments (e.g., create a cython module with > a cached method, recompile sage, and then remove the source of the > module) in order to find out if there is a way around (and if I can > replicate the problem).
In two experiments with Sage-6.5.beta4, I can not replicate the problem. What I did first: I created a pyx file containing a cdef class derived from sage.structure.parent.Parent, with a cached method. I attached that file and then moved it to somewhere else (triggering the message "### detaching file ..."). Both using the cached method and introspection of the cached method did work. Attaching the file creates a copy of that file in a temporary folder, and that copy is what is used for introspection. So, in the next test, I deleted that temporary copy AND the original file. As a result, inspecting the source code of the cached method did not work (as expected), it displayed the code of sage.misc.cachefunc.cached_method rather than the code of my method. However, *calling* the method was no problem, and the cache worked! Best regards, Simon -- 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. For more options, visit https://groups.google.com/d/optout.
