On Fri, Apr 15, 2011 at 3:54 PM, John Hunter wrote:
>
>
> On Fri, Apr 15, 2011 at 3:42 PM, Benjamin Root wrote:
>
>>
>> There might be a possible work-around, though. Maybe (and I am just
>> speculating here) if we can get the core part of matplotlib to specially
>> treat 3d collection objects
On Fri, Apr 15, 2011 at 3:42 PM, Benjamin Root wrote:
>
> There might be a possible work-around, though. Maybe (and I am just
> speculating here) if we can get the core part of matplotlib to specially
> treat 3d collection objects in such a way that allows the collection to
> return provide elem
On Mon, Apr 11, 2011 at 4:16 AM, Konrad Bartkowski <
k.bartkow...@fz-juelich.de> wrote:
> Ok, forwarding it to the matplotlib-devel list.
>
>
> Best wishes,
>
> Konrad (on behalf of our workgroup)
>
>
> Original Message Subject: Source of inaccuracies in the
> matplotlib librar
On Fri, Apr 15, 2011 at 9:27 AM, Jouni K. Seppänen wrote:
> Benjamin Root writes:
>
> > Would a change to the v1.0.x branch "stay" on the v1.0.x branch, or is
> > there something I have to do to prevent subsequent merges from going
> > into master?
>
> Since v1.0.x is supposed to be merged into
Benjamin Root writes:
> Would a change to the v1.0.x branch "stay" on the v1.0.x branch, or is
> there something I have to do to prevent subsequent merges from going
> into master?
Since v1.0.x is supposed to be merged into master frequently, your
change would propagate into master. To prevent i
