I think I wrote this one thousand times in the sage-devel thread, but 1) I am not against decorators (I hate them, but that's not a sufficient reason for preventing other people to use them) 2) I am not against find_stat 3) Some of the information that you may add in Sage can be useful (though until now I only saw this information mentionned as "future features")
What I claim is that you can make all this work without making Sage compute things that are only necessary for find_stat, even when find_stat is not what the users want to use. You can do so by adding information to the docstrings, or by rewriting your decorator such that it returns exactly the function that it is given, and does not wrap it with a class. Hence, because I understand that my sentences are very very long and use many words : Decorators : Yes Find_stat : Yes Additional Information : Yes Additional Computational Cost for these features : No, because there is a way to avoid it. Could we continue this on Sage-devel ? Nathann -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel. For more options, visit https://groups.google.com/groups/opt_out.
