Hi Derek,
--- On Sun, 4/14/13, Derek Homeier wrote:
> Of course if there are any other possible negative effects
> besides the window handling, I'd take your point.
Several bugs have been reported in the past that turned out to be due to Python
not being installed as a framework. For example, t
Hi Michiel,
> This RuntimeError is there for a reason: If your Python is not installed as
> a framework, the backend will not work correctly (and if you ignore the
> RuntimeError, you won't know if any problems you encounter are real bugs, or
> simply due to your Python not being installed as
Hi Derek,
--- On Sun, 4/14/13, Derek Homeier wrote:
> The RuntimeError was enforced by the #ifdef
> WITH_NEXT_FRAMEWORK check that
> does not allow to use the backend at all, so I had to change
> this to a RuntimeWarning
> to be able to test the backend in the 1.3 branch.
This RuntimeError is th
Hi Michiel,
> That is good to hear.
> The slowdown was caused by the performance of Quartz itself, but it depends
> strongly on the line width. In your example, the plot appears immediately if
> you use linewidth=0.9, but (with matplotlib 1.2.1) takes minutes to appear if
> you use linewidth=1.
