During my attempts at C elimination, I see that atan2 is involved in
many potential import cycles.
Of these, most if not all can be broken up by splitting up
sympy.functions.elementary.trigonometric , e.g. by splitting off
sympy.functions.elementary.trigonometric_inverses.
Such a split is not a guarantee that it will prevent all present or
future atan2 cycles, because there's always the possibility of mutual
recursion between modules.
The alternate approach would be to use a local import, or a bottom import.
I'd prefer to split the module in this case, because it's a reasonable
module boundary anyway.
What do others think?
--
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/54E05B66.3070505%40durchholz.org.
For more options, visit https://groups.google.com/d/optout.
