Volker Braun wrote: > My advice would be to implement the parent in Python and benchnmark > it. If you are doing something in _element_constructor_ that would > benefit greatly by Cython then you can just move that part to Cython.
Apparently my question was unclear. Of course, it is good advice as a general rule decide based on profiling results. But: _assuming_ not only that parts of what _element_constructor_ does benefit from Cython, but also that the cost of issuing a Python method call when constructing elements is significant, what is the best approach to deal with it? Or, to put it differently: why are so many parents Cython classes if there are no benefits? -- Marc -- 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.
