matplotlib-devel Mailing List for matplotlib

On Wed, Sep 19, 2012 at 6:53 PM, Michael Droettboom <md...@st...> wrote:
> I have tagged and created a tarball for 1.2.0rc2. The githash is
> 656c88f3e546. The tarball is on the github download page here:
>
> https://github.com/matplotlib/matplotlib/downloads
>
> This includes a number of important bugfixes, including things required
> for creating Macintosh and Windows binaries. The Travis tests are also
> now passing.
>
> I hope it will be easier for the binaries to be created this time. Once
> they are available at github, I will make an announcement to
> matplotlib-users and hopefully get some serious testing out of this thing.
>
> Thanks for all of the hard work!
>
> Mike
The website says the current development version is rc1.
-- 
Damon McDougall
http://www.damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom

On Sat, Sep 22, 2012 at 10:40 AM, Damon McDougall
<dam...@gm...> wrote:
> Ah ok, I see. I was assuming a plot_trisurf(x, y, z, triangles, ...)
> signature. Copying the tricontour signature would be better for
> consistency reasons. It appears that I was the one missing something!
I just realised I'm not making any sense here. Please disregard most
of what I say.
I'm using the get_from_args_and_kwargs method and everything is fine.
-- 
Damon McDougall
http://www.damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom

On Fri, Sep 21, 2012 at 2:38 PM, Benjamin Root <ben...@ou...> wrote:
> I wouldn't be against going down a deprecation path for renaming these
> functions, but for what gains? The names have been there since before I
> took up this toolkit, and ultimately, these functions aren't typed so often
> that brevity would gain one much. Definitely any new functions should not
> take up that naming, but I see no real compelling reason to change the
> existing names.
Technically, 1.2 hasn't been released yet. We can still change
plot_trisurf to trisurf, though it appears there is still uncertainty
regarding whether there will actually be a third release candidate.
-- 
Damon McDougall
http://www.damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom

On Fri, Sep 21, 2012 at 6:21 PM, Ian Thomas <ian...@gm...> wrote:
> I am happy with option 3 too, but I don't think you need to do as much as
> this. The existing 2d triplot/tripcolor/tricontour call
> Triangulation.get_from_args_and_kwargs, which removes the various
> args/kwargs needed for the triangulation and leaves the remainder for the
> calling function to process. For example lib/matplotlib/tri/tricontour.py
> lines 86 to 88:
>
> tri, args, kwargs = \
> Triangulation.get_from_args_and_kwargs(*args, **kwargs)
> z = np.asarray(args[0])
>
> Can't you just do the same here, or am I missing something?
Ah ok, I see. I was assuming a plot_trisurf(x, y, z, triangles, ...)
signature. Copying the tricontour signature would be better for
consistency reasons. It appears that I was the one missing something!
Thanks for that.
-- 
Damon McDougall
http://www.damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom