Yeah, Pyglet is very problematic, especially on Mac OS X. There is indeed work on moving to other backends, primarily matplotlib. See https://github.com/sympy/sympy/pull/673, and also search this mailing list for threads about it.
There is a GSoC idea to extend this framework. By the way, the latest version of Pyglet was released in 2010, but there have been active updates in the mecurial repository at http://code.google.com/p/pyglet/. Does the development version work any better? For the equation editor, you need to decide what framework you will use for it. I think for now, we should either go for something curses based or web based. The former would hook into the current pretty printing system. The latter would be something to add into SymPy Live. Hopefully it could also be hooked into the IPython notebook as well, though I dont know to what level they allow extensions like that (you'll have to ask on their list). If extensions are possible in the qtconsole, that would be an idea too, I guess. Aaron Meurer On Fri, Mar 23, 2012 at 10:56 PM, Vishesh Kumar <[email protected]> wrote: > I've spent the entire week trying to get pudb, winpdb, and sympy's plot to > work on my macbook pro (OS X 10.6.8), and alternatively in Ubuntu 11 in a > virtual machine. I managed to get winpdb and pudb to work. Sympy's plot, > almost entirely doesn't. As far as I can tell, lots of digging tells me this > is Pyglet's fault. > The furthest I managed is, by executing pl.py, a program to plot(x**2) (and > some slight variants of it), by entering arch -i386 python2.6 pl.py, I > finally got a plot. But the python window that opens up, without fail, > refuses to respond. > It sounds ambitious to me, but Pyglet has lots of issues on almost all kinds > of machines – what is the possibility of trying to shift to a different > rendering engine? Could I work on that as my GSoC project? > All the functions worked as described on a certain friend's machine, but in > no instance on my computer. So it might be the fault of somethings I've > installed beforehand etc., but I think that's pretty unlikely, because all > errors I get (whenever I did get an error, and it wasn't just python > hanging), seem to be Pyglet's issues. > > Would you say I furnish you with more details? Or can working on an equation > editor work as an entire GSoC project? In any way, I would be grateful to > receive some direction on how to start off with that (the equation editor). > > Regards > Vishesh Kumar > > > On Saturday, 17 March 2012 01:34:43 UTC+5:30, Vishesh Kumar wrote: >> >> I am interested in working at the equation editor task and/or improving >> the plotting module, as possible projects for GSoC 2012. >> I would love to know how to start out with either, and what aspects I >> should approach. With regard to the plotting module, it seems like a vast >> thing in entirety, but I don't know if we'd be required to work on all of it >> or choose some subset of that. In either case, I don't have much idea of the >> same by default, and would be grateful to receive some initial guidance, >> with regard to starting off. >> >> ------------------- >> Regards >> Vishesh Kumar > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/sympy/-/jFAEywPqU0sJ. > > To post to this group, send email to [email protected]. > 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. -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. 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.
