I'll note also that there is a 7 year old(!) open ticket about this at: https://trac.sagemath.org/ticket/13071
I think it would be a very good problem to solve (maybe a GSoC student could do it?) ISTM this should be possible by, given a symbolic expression, going through it and renaming any symbolic variables/functions in it that are known (or can be detected to?) conflict with functions in Maxima before actually passing it to Maxima. That, or detecting the problem when it occurs and automatically falling back to a different integration backend where possible (possibly with a warning). I think the former would be a better solution long-term, but it would be good to at least have a fix for this that doesn't result in a useless exception returned to users. On Sat, Feb 23, 2019 at 6:57 PM Richard_L <richar...@lozestech.com> wrote: > > Thanks, Eric. > I never would have guessed that I could not use the most common notation in > quantum mechanics! > > -- > 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. -- 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.
