On Wednesday, 21 October 2015 07:47:21 UTC+2, Justin wrote: > > Here are some of the changes that were requested. I will continue to work > but I'm afraid I'm going to need to take a full day to work out the SymPy > Expr Tree (focusing on vectors) to do any kind of symbolic vector > programming. Here is the link to my commit: > > > https://github.com/jbbskinny/sympy/commit/793539fe13c1136750452a8796b16a5516863d51 > > -- Forked from Upabjojr/sympy:vector_all_coord_sys > > Oh, that's nice.
Create a PR, so we can comment on the code there. I'd also suggest to fork the master branch if your edit is unrelated to mine, unless you want to go on with my PR. Also have a look at: http://docs.sympy.org/latest/modules/utilities/runtests.html > This is fixed in Python and is not something we can change. My opinion is >> that overloading the operators like this at all is a bad idea in Python. >> I'd rather not have them there at all. >> > > Out of curiosity, which Python function does this? Adding a whole new > operator is interesting.. and, of course, debatable. > Defining a new operator is a very fast operation, you just add a new method to a class. The drawback is that debugging the code becomes less clear, if you are not familiar it also gets less readable, compare *del*r* to *gradient(r)*, the latter is straightforward, while the first is a little harder to read. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/cef11e2e-9dc3-446d-b33a-0a2a90537ca6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
