On Monday, July 23, 2012, Eric Firing wrote:
> On 2012/07/23 11:43 AM, Damon McDougall wrote:
> > Hello all,
> >
> > So, as per Philip's suggestion
> > (https://github.com/matplotlib/matplotlib/pull/737) I've started
> > encapsulating fplot functionality into a class. The point of this is so
> > t
On 2012/07/23 11:43 AM, Damon McDougall wrote:
> Hello all,
>
> So, as per Philip's suggestion
> (https://github.com/matplotlib/matplotlib/pull/737) I've started
> encapsulating fplot functionality into a class. The point of this is so
> that the user can call either of the following:
>
> FPlot_ins
Hello all,
So, as per Philip's suggestion
(https://github.com/matplotlib/matplotlib/pull/737) I've started
encapsulating fplot functionality into a class. The point of this is so
that the user can call either of the following:
FPlot_instance = ax.fplot(f, [x0, y0, x1, y1])
ax.fplot(FPlot_instance
On Fri, Jul 20, 2012 at 3:21 PM, John Hunter wrote:
> I would like to discuss a timetable towards a python3 release (1.2 or
> 2.0). I'll throw this out there, and am happy to make modifications
> according to feedback
>
> Aug 20th : feature freeze and branch. bugfixes only going forward from
>
Dear macosx backend users,
Could you please have a look at pull request
https://github.com/matplotlib/matplotlib/pull/1036. It removes a minor
annoyance where only the last figure would appear to the front after
issuing a non-interactive show().
It builds upon https://github.com/matplotlib/mat
