VulK writes: > The first question is about which is the correct way to implement methods > that are not always defined.
I agree with Nils that subclassing is the most OOP-clean way of achieving this. That being said, one might argue that it is a pretty heavy-handed solution which potentially leads to class-explosion and mega-multiple-inheritance. Another possibility is to do the converse of what you are doing: add the method on the class but *delete* at construction time if it is not appropriate. This can be done using delattr. VulK writes: > The second problem is a little more involved, I will try to give you a souped > up version here. > ... Did you take a look at performing the preparsing using a decorator which properly uses @sage_wraps? It is possible to do the documentation modification at decoration-time, and then it should properly show up in Sphinx as well. Best, Johan -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
