On Fri, Apr 27, 2012 at 2:54 PM, [email protected] <[email protected]> wrote: > Sometime ago I mentioned that for the correct working of the new > plotting module (actually only for the matplotlib backend) one must do > some magic with the event loops. It seems that this magic was so hard > that the matplotlib documentation simply states that if you want > interactive non-blocking plotting you _must_ use ipython as the > ipython team has taken care of all this. So, now the implementation of > the new plotting module requires a small one line change to the sympy > profile in ipython. > > I will leave the discussion surrounding all the event loop magic and > plotting for another time and focus on the problem of updating the > sympy profile in ipython. > > The fact is that one needs to add different new configuration options > to this profile as sympy evolves and it is suboptimal to require an > upstream change in ipython for every such change. > > To remedy this problem Aaron proposed some time ago to dump all such > configurations in the interactive module in sympy and just make the > ipython's sympy profile call them. > > Could we proceed with this idea?
Yes, let's do it. Will you be able to do it? The relevant SymPy issues are 3031, 2632, and 2945. Aaron Meurer -- 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.
