Comment #39 on issue 1233 by [email protected]: fix the rest of jython bugs http://code.google.com/p/sympy/issues/detail?id=1233
My guess (could be way off): they are trying to apply some kind of import optimization that is incorrect somehow, leading to a circular import error where there shouldn't be one. If you look at a real circular import error, it looks the same way: like it is failing to import something that should have already been imported. Given how complicated SymPy's import graph is, it isn't too surprising that they wouldn't have already caught something like this.
If you really want to know, you could try bisecting the Jython history. Like I said, I don't have the heart for it. Or we could ask the Jython devs for insight.
-- You received this message because you are subscribed to the Google Groups "sympy-issues" 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-issues?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
