Maybe we should change approach to the coordinate systems. Implementing the code inside the *vector* module may end up messing up everything.
What about a separate module to handle coordinate system properties in a new-style assumption manner? One could have assumptions like: - Qcoord.is_spherical(vector) - Qcoord.belongs_to_coord_system(vector, coord_system_object) - Qcoord.has_laplacian(coord_system_object, Lambda_for_laplacian) - Qcoord.connect_coord_system(coord_system1, coord_system2, transformation_function) It's quite complicated to specify all these properties upon class creation, it would need lots of parameters. Connecting a coordinate system to a Cartesian one fully specifies (mathematically) how the operators (gradient, divergence, curl) operate, but one could just wish to specify the form of the operators, without specifying the transformation function. I believe an assumptions systems is a good way to handle coordinate systems. It could in principle also be extended to the matrix module. -- 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 https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/21d9a47a-6ca5-46d3-ad94-a2377a8abe66%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
