Hi Michiel,
On 16.04.2013, at 12:03AM, Michiel de Hoon wrote:
> Can you perhaps ask the Fink developers to provide a framework installation
> of Python? Most matplotlib users who ran into framework-related bugs were
> Fink users.
I've already looked for that in the list archives and it seems
Hi Derek,
Can you perhaps ask the Fink developers to provide a framework installation of
Python? Most matplotlib users who ran into framework-related bugs were Fink
users.
Best,
-Michiel.
--- On Mon, 4/15/13, Derek Homeier wrote:
> From: Derek Homeier
> Subject: Re: [matplotlib
Hi Michiel,
On 15.04.2013, at 6:03AM, Michiel de Hoon wrote:
> --- 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 d
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.
ct: Re: [matplotlib-devel] Planning for 1.3.0
> To: "matplotlib development list"
> Date: Saturday, April 13, 2013, 9:03 AM
> Hi Michiel,
>
> On 13.04.2013, at 1:30AM, Michiel de Hoon wrote:
>
> > The slow speed for long paths like the one in your
> example was
Hi Michiel,
On 13.04.2013, at 1:30AM, Michiel de Hoon wrote:
> The slow speed for long paths like the one in your example was due to a
> limitation to Quartz itself. This was solved by breaking the path up into
> subpaths of up to 100 points. But you mentioned that releases before 1.2 were
> n
), suggesting that something
else is going on. Can you check which change between 1.1.1 and 1.2 is causing
the slowdown for your example?
Best,
-Michiel.
--- On Fri, 4/12/13, Derek Homeier wrote:
> From: Derek Homeier
> Subject: Re: [matplotlib-devel] Planning for 1.3.0
> To: "ma
On 11.04.2013, at 6:38PM, Michael Droettboom wrote:
> Congrats to everyone on a successful 1.2.1 -- there was a relatively
> small influx of bug reports following it -- perhaps a sign of improving
> quality?
Thanks and congratulations to everyone involved as well; I've built 1.2.1 on
MacOS X
Great news! A lot of fantastic work has been done by a whole host of people
to go into this release. It's exciting stuff!
May 27th sounds like a sensible target to me. As you know, I'm an advocate
of releasing often - the more frequently we make a release, the less we
will have the "impending rele
12 matches
Mail list logo
