>> OK, so to move things forward, the reason for using a particular >> mpmath and a particular pyglet is that those are versions that are >> known to work with sympy. > > IMHO sympy should just work with the latest stable version of pyglet/ > mpmath. Of course this means that someone needs to fix sympy when > there's something fundamentally changed in a third party package. I > would prefer this solution, but if it's a too big effort let's include > our own versions. > >> So let's try to figure out how to use pyglet without touching >> sys.path. If we succeed, is anyone against leaving both mpmath and >> pyglet in sympy? > > As I said I don't like this solution but it's the way to go if > otherwise it would be too difficult to maintain .
Why do you not like it? Because of the size of the included files? There shouldn't be any other side effect. > >> If we fail, then we'd have to release two tarballs, one with, the >> other without, pyglet. >> > > What's so wrong with sys.path hacking? Because it's leaving side effects for the user, which is very, very bad. Also it does't work always, for example on the google app engine. Ondrej --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
