Note that Cython supports cProfile these days: http://docs.cython.org/src/tutorial/profiling_tutorial.html However, that won't help too much as the real missing pieces are the calls from Cython into the various C libraries.
I'm also -1 to an approach that slows down all of Sage to track this unconditionally. The decorator approach could be good for annotating functions (e.g. attaching them to some database the citations module would use) but recording every call could be prohibitively expensive. As far as the question of why software isn't cited, usually the metric of "usefulness" is #downloads. If you're established enough that downloads typically come via a distribution of sorts (e.g. Sage) then that is another data point for being useful. This adds to the difficulty of getting academic credit for programming work. On Sat, Sep 6, 2014 at 11:04 AM, Volker Braun <vbraun.n...@gmail.com> wrote: > On Saturday, September 6, 2014 5:44:57 PM UTC+1, Bill Hart wrote: >> >> It takes samples at regular points during the computation > > > Thats the aforementioned http://trac.sagemath.org/ticket/16777. See that > ticket for technical obstacles of that approach. > > -- > 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. -- 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.
