Hi, I sent a patch implementing Basic.simplify():
http://groups.google.com/group/sympy-patches/browse_thread/thread/af95cd2b52745d2b and we should discuss it with everyone, let's discuss it here. Fabian: " I'm 0 for this. Don't see the need for this, I think that there are already too many classmethods for Basic, and having sympify as a classmethod and as a static method (same name, different arguments expected) would only confuse users ... " Ondrej: " Yeah. I find it handy sometimes, but I agree with your point. Others, what do you think? " Vinzent: " I think we should really decide which methods should be kept as class methods and which not. I don't like it for example that all linear algebra functions are an attribute of Matrix. Currently, it doesn't seem to be systematic or consistent. Maybe we should discuss * when to use class methods * when to use static methods and * when to use both. Are there important reasons or motivations? " Let's get this discussed. We had this discussion before already: http://groups.google.com/group/sympy/browse_thread/thread/f59919f28cfd2df6/843689054b06e55c#843689054b06e55c But since sympy has matured a lot since then, it's time to revise it again. Now I tend to think that only the very basic stuff should be part of Basic and everything else should be implemented using regular functions. In Mathematica you also can do everything using functions. That way we can easily extend sympy and add more modules. We can add deprecation warnings into Basic.limit() or Basic.integrate(). What do you think? Ondrej --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
