matplotlib-devel Mailing List for matplotlib (Page 2)

I'm using v1.5.1 and I was reading the discussion on
https://github.com/matplotlib/matplotlib/pull/3652
and trying to reproduce the toolbar manipulation shown at
https://github.com/fariza/pycon2015/blob/master/ToolDemo.ipynb
I can't get it to work from either regular python or ipython
(console), at least not with my WXagg, GTKagg or GTKCairo backends.
In my matplotlibrc I have set toolbar to be toolmanager.
After successfully getting a figure window with fig, ax =
plt.subplots(), I find that fig.canvas.manager.toolbar is None and
there is no toolmanager attribute in the manager.
Did I miss something that has changed, because the pull seemed to
apply to 1.5.1?
Thanks,
Rob

Well... this is a *really* late reply, but I finally got around to adding
easier navigation for the style gallery
<https://tonysyu.github.io/raw_content/matplotlib-style-gallery/gallery.html>.
I
also added an update for styles added in Matplotlib 1.5 and wrote a quick
post <https://tonysyu.github.io/matplotlib-style-gallery.html#.VvoAzxIrKV4>.
Cheers!
-Tony
On Thu, Jan 8, 2015 at 8:10 PM, Tony Yu <ts...@gm...> wrote:
> Thanks Max!
>
> I was planning to add a more interactive interface, really similar to what
> you're suggesting. I haven't gotten around to it, but hopefully, I'll have
> some time to play around with that.
>
> On Thu, Jan 8, 2015 at 4:56 PM, Maximilian Albert <
> max...@gm...> wrote:
>
>> Hi Tony,
>>
>> This is awesome. Great work!
>>
>> I was wondering, is there an easy way to cycle through all available
>> styles for a given plot? For instance, clicking on the top left plot
>> displays a maximized image of the "bmh" style. It would be great if one
>> could press arrow-down (say) to cycle through the other styles
>> "dark_background", "fivethirtyeight", etc. for a quick comparison.
>>
>> Cheers,
>> Max
>>
>>
>> 2015年01月06日 4:42 GMT+00:00 Tony Yu <ts...@gm...>:
>>
>>> I've been playing around with learning Javascript lately. As part of the
>>> process, I created a Flask app to build a gallery for matplotlib style
>>> sheets:
>>>
>>> https://github.com/tonysyu/matplotlib-style-gallery
>>>
>>> If you run that locally, you can actually input styles, either with a
>>> URL to a *.mplstyle file or with matplotlibrc commands. Here's a static
>>> version without the custom inputs:
>>>
>>>
>>> http://tonysyu.github.io/raw_content/matplotlib-style-gallery/gallery.html
>>>
>>> Ideally, I'd get this into a form that could be submitted as a PR for
>>> the matplotlib website, but I'll need a bit more spare time to learn some
>>> more web development (sessions, client storage, etc).
>>>
>>> Cheers!
>>> -Tony
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Dive into the World of Parallel Programming! The Go Parallel Website,
>>> sponsored by Intel and developed in partnership with Slashdot Media, is
>>> your
>>> hub for all things parallel software development, from weekly thought
>>> leadership blogs to news, videos, case studies, tutorials and more. Take
>>> a
>>> look and join the conversation now. http://goparallel.sourceforge.net
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>>
>>
>

Hi all,
[ please direct all replies directly to me ]
Project Jupyter is announcing the opening of a position for a full-time
project manager, who will help us coordinate our technical development,
engage the open source community and work with our multiple stakeholders in
academia and industry.
If you have experience leading technical teams in open source communities,
we'd love to hear from you! In the last few years the project has rapidly
grown in multiple directions, and this presents both challenges and
opportunities. We are looking for someone who can help us harness the
energy and activity from our many contributors that include those funded by
our research grants, our industry partners, and the entire open source
community.
The role of the project manager is to help us maintain this activity
focused into a solid whole, so we can deliver timely and robust releases,
evolve our architecture coherently, ensure our documentation and
communication matches our technical foundation, and continue engaging a
wide range of stakeholders to evolve the project in new, interesting and
valuable directions.
This position will be hosted at the Berkeley Institute for Data Science,
working locally with Fernando Perez, Matthias Bussonnier, and our new
postdoctoral scholars. But the scope of this role is the entire project, so
we are looking for a candidate who will be regularly communicating with
project stakeholders from all locations, traveling to conferences,
development workshops and other project activities.
For specific details on the position and to apply, you can learn more at
jobs.berkeley.edu, Job ID #20975:
https://hrw-vip-prod.is.berkeley.edu/psc/JOBSPROD/EMPLOYEE/HRMS/c/HRS_HRAM.HRS_CE.GBL?Page=HRS_CE_JOB_DTL&Action=A&JobOpeningId=20975&SiteId=1&PostingSeq=1&
Note that while the application review date is listed as January 1, 2016,
we will be considering applicants past that date (that is the cutoff for us
to be allowed to look at incoming applications). The search will remain
open until filled.
-- 
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail

Hi all,
We are delighted to announce today that Project Jupyter/IPython has two
postdoctoral fellowships open at UC Berkeley, open immediately. Interested
candidates can apply here:
https://aprecruit.berkeley.edu/apply/JPF00899
We hope to find candidates who will work on a number of challenging
questions over the next few years, as described in our grant proposal here:
http://blog.jupyter.org/2015/07/07/project-jupyter-computational-narratives-as-the-engine-of-collaborative-data-science/
Interested candidates should carefully read that proposal before applying
to familiarize themselves with the full scope of the questions we intend to
tackle.
We'd like to thank the support of the Helmsley Trust, the Gordon and Betty
Moore Foundation and the Alfred P. Sloan Foundation.
Cheers,
Brian Granger and Fernando Perez.
-- 
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail

Congratulations, Mike! This is great news for the community!
On Wed, Sep 30, 2015 at 10:25 AM, Nelle Varoquaux <nel...@gm...
> wrote:
> Congrats on the new position!
>
> On 30 September 2015 at 14:18, Michael Droettboom <md...@st...> wrote:
> > Just a heads up to the matplotlib developer team:
> >
> > I'm leaving Space Telescope for a new position at Continuum Analytics
> > starting next week. This position will be primarily to work on
> > matplotlib, so I should have much more time to participate than I have
> > in recent years. Thomas Caswell and I have already met to discuss how
> > we can best share some of the mountains of work that he's been doing and
> > help me transition to being more involved again.
> >
> > I think it bears saying, just to be clear, that Continuum in no way
> > change how matplotlib is run by their support of my time. It will
> > remain an open community project where anyone with a good idea can
> > participate and contribute. It is very important to me that it remains
> > that way, and it is very important to Continuum's leadership as well.
> >
> > Let me know if you have any questions. I really look forward to being
> > more involved with all the great work that's going on here!
> >
> > Cheers,
> > Mike
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Matplotlib-devel mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Congrats on the new position!
On 30 September 2015 at 14:18, Michael Droettboom <md...@st...> wrote:
> Just a heads up to the matplotlib developer team:
>
> I'm leaving Space Telescope for a new position at Continuum Analytics
> starting next week. This position will be primarily to work on
> matplotlib, so I should have much more time to participate than I have
> in recent years. Thomas Caswell and I have already met to discuss how
> we can best share some of the mountains of work that he's been doing and
> help me transition to being more involved again.
>
> I think it bears saying, just to be clear, that Continuum in no way
> change how matplotlib is run by their support of my time. It will
> remain an open community project where anyone with a good idea can
> participate and contribute. It is very important to me that it remains
> that way, and it is very important to Continuum's leadership as well.
>
> Let me know if you have any questions. I really look forward to being
> more involved with all the great work that's going on here!
>
> Cheers,
> Mike
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Congrats Mike!
Sent from my iPhone
> On Sep 30, 2015, at 8:18 AM, Michael Droettboom <md...@st...> wrote:
> 
> Just a heads up to the matplotlib developer team:
> 
> I'm leaving Space Telescope for a new position at Continuum Analytics 
> starting next week. This position will be primarily to work on 
> matplotlib, so I should have much more time to participate than I have 
> in recent years. Thomas Caswell and I have already met to discuss how 
> we can best share some of the mountains of work that he's been doing and 
> help me transition to being more involved again.
> 
> I think it bears saying, just to be clear, that Continuum in no way 
> change how matplotlib is run by their support of my time. It will 
> remain an open community project where anyone with a good idea can 
> participate and contribute. It is very important to me that it remains 
> that way, and it is very important to Continuum's leadership as well.
> 
> Let me know if you have any questions. I really look forward to being 
> more involved with all the great work that's going on here!
> 
> Cheers,
> Mike
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Just a heads up to the matplotlib developer team:
I'm leaving Space Telescope for a new position at Continuum Analytics 
starting next week. This position will be primarily to work on 
matplotlib, so I should have much more time to participate than I have 
in recent years. Thomas Caswell and I have already met to discuss how 
we can best share some of the mountains of work that he's been doing and 
help me transition to being more involved again.
I think it bears saying, just to be clear, that Continuum in no way 
change how matplotlib is run by their support of my time. It will 
remain an open community project where anyone with a good idea can 
participate and contribute. It is very important to me that it remains 
that way, and it is very important to Continuum's leadership as well.
Let me know if you have any questions. I really look forward to being 
more involved with all the great work that's going on here!
Cheers,
Mike

Hi all,
I see in the matplotlib 1.5 release notes that the figures created via the
OO interface can now be interactively updated.
Does this mean it's now possible to create a figure using the interactive
backend, manually associate it with a figure manager, and then call the
show() method on the figure manager to display the plot in an interactive
window, all without (possibly indirectly) importing pyplot? If not, should
I just give up and do this via pyplot? I'd like to avoid importing pyplot
if possible to avoid crashes on headless sessions.
Thanks for your help or advice,
Nathan

Hi all,
I would like to set up a Travis build of seaborn that tests against the
development version of matplotlib. Ideally this would happen without
actually compiling matplotlib on Travis, to save time.
Does matplotlib master get packaged such that it is installable through
conda? I thought I recalled seeing this somewhere, but I am having trouble
digging it up.
Thanks!
Michael

There is the concept of clipping. We can choose to clip artists to a
bounding box. There has been some back-n-forth on whether or not
annotations should be clipped. I can't remember what we have decided on,
but that example definitely looks like evidence that they should be clipped.
By the way, please use the new python.org mailing lists.
On Thu, Aug 20, 2015 at 1:59 PM, Andrés Vargas <and...@gm...> wrote:
> Hello,
>
> I am writing to let you know guys that while implementing a backend I run
> into an issue when doing panning. Which render the texts outside the axes.
> I tried to solve it but I had no way to know if the text is either from
> inside the axes or outside. I think this perhaps need a change in
> backend_bases. I looked into the other backends and they have the same
> problem even GtkCairo.
>
> http://imagebin.ca/v/2Coe4Nzw3hZl
>
> The problem can be seen on there with the text inside the axes.
>
> Thanks, Andres
>
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Hello,
I am writing to let you know guys that while implementing a backend I run
into an issue when doing panning. Which render the texts outside the axes.
I tried to solve it but I had no way to know if the text is either from
inside the axes or outside. I think this perhaps need a change in
backend_bases. I looked into the other backends and they have the same
problem even GtkCairo.
http://imagebin.ca/v/2Coe4Nzw3hZl
The problem can be seen on there with the text inside the axes.
Thanks, Andres

Did you mean 1.4.1 instead of 1.5.1 ?
Exactly which paths are you looking at and how are you generating then on
the mpl side? We have many ways to generate the paths and there maybe
inconsistence in how closed paths are handled.
Tom
On Wed, Aug 12, 2015, 1:57 PM Andrés Vargas <and...@gm...> wrote:
> Hello,
>
> My name is Andres I am developing a backend for kivy. I was initially
> developing for 1.5.1 and I found that the paths are coming with the initial
> vertex at the end of the list. Does anyone know whether this is change in
> the way paths are sent ? and how can be fixed coming from 1.4.3 since I am
> developing the backend for that version.
>
> Thanks, Andres
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hello,
My name is Andres I am developing a backend for kivy. I was initially
developing for 1.5.1 and I found that the paths are coming with the initial
vertex at the end of the list. Does anyone know whether this is change in
the way paths are sent ? and how can be fixed coming from 1.4.3 since I am
developing the backend for that version.
Thanks, Andres

If I remember correctly, draw_gouraud_triangle is used by tripcolor when
shading='gouraud'. Basically, it's a gradient mesh in Adobe terms. I'm
sure it's used in a few other places as well.
As for why it's not implement in some backends, it's probably either an
oversight, or gradient meshes aren't natively supported by that particular
toolkit (I would guess the latter).
Finally, as far as the text rotation goes, it depends on value of
text.get_rotation_mode(). The default value is to apply the rotation
first, and then deal with horizontal/vertical alignment. However, a value
of "anchor" will correspond to rotation about the bottom-left position.
See:
http://matplotlib.org/examples/pylab_examples/demo_text_rotation_mode.html
for an illustration.
Hope that helps a bit!
-Joe
On Mon, Aug 10, 2015 at 11:15 AM, Andrés Vargas <and...@gm...> wrote:
> Hello,
>
> Sorry does anyone know what is draw_gouraud_triangle for when you write a
> backend ?
> I am trying to find examples for this but not finding any.
> Also why is this not implemented for gtk, wx and qt ?
> I would also appreciate to know whether the rotation of the text is
> relative to the bottom-left position or the center ?
>
> Thanks :)
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Hello,
Sorry does anyone know what is draw_gouraud_triangle for when you write a
backend ?
I am trying to find examples for this but not finding any.
Also why is this not implemented for gtk, wx and qt ?
I would also appreciate to know whether the rotation of the text is
relative to the bottom-left position or the center ?
Thanks :)

Thanks Mike. I haven't had a chance to investigate further, but when I
do I will look at pkg-config...
On Fri, Jul 31, 2015 at 2:26 PM, Michael Droettboom <md...@st...> wrote:
> Sorry for the delayed response.
>
> I had a discussion thread with Aaron Meurer last year about adding
> pkg-config support to anaconda so that matplotlib would build
> out-of-the-box, but I don't think that's gone anywhere. That would allow
> the extensive patches in the anaconda matplotlib recipe (and probably many
> other recipes for C and Unixy packages) to go away. (Note that the
> "pkgconfig" Python package in Anaconda is just the Python wrapper to the
> underlying Unix tool which is not present in Anaconda).
>
> Mike
>
>
> On 07/22/2015 07:52 PM, Nathan Goldbaum wrote:
>
> One way to do this is to build a Conda package using the matplotlib recipe:
>
> https://github.com/conda/conda-recipes/tree/master/matplotlib
>
> Looking at the Conda recipe might give you some hints about how it locates
> png.h as well, although I haven't checked in detail.
>
> On Wednesday, July 22, 2015, Brian Granger <ell...@gm...> wrote:
>>
>> No I am fine linking against the stuff that ships with conda - just
>> not clear on how to get the setup.py logic to look in the right place.
>>
>> On Wed, Jul 22, 2015 at 11:20 AM, Phil Elson <pel...@gm...> wrote:
>> > Are you wanting to link against anything other than that installed with
>> > conda?
>> > The output of setup.py is normally pretty helpful at letting you know
>> > which
>> > library it has found to build against.
>> >
>> > On 20 July 2015 at 01:54, Brian Granger <ell...@gm...> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I am trying to get a dev build of matplotlib working with the anaconda
>> >> python.
>> >>
>> >> Any advice on getting matplotlib to detect and use any of the
>> >> libpng/freetypes:
>> >>
>> >> * Those installed with anaconda python.
>> >> * Those from homebrew
>> >> * Those that ship with OS X
>> >>
>> >> Cheers,
>> >>
>> >> Brian
>> >>
>> >> --
>> >> Brian E. Granger
>> >> Cal Poly State University, San Luis Obispo
>> >> @ellisonbg on Twitter and GitHub
>> >> bgr...@ca... and ell...@gm...
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Don't Limit Your Business. Reach for the Cloud.
>> >> GigeNET's Cloud Solutions provide you with the tools and support that
>> >> you need to offload your IT needs and focus on growing your business.
>> >> Configured For All Businesses. Start Your Cloud Today.
>> >> https://www.gigenetcloud.com/
>> >> _______________________________________________
>> >> Matplotlib-devel mailing list
>> >> Mat...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>> >
>> >
>>
>>
>>
>> --
>> Brian E. Granger
>> Cal Poly State University, San Luis Obispo
>> @ellisonbg on Twitter and GitHub
>> bgr...@ca... and ell...@gm...
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
-- 
Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgr...@ca... and ell...@gm...

Sorry for the delayed response.
I had a discussion thread with Aaron Meurer last year about adding 
pkg-config support to anaconda so that matplotlib would build 
out-of-the-box, but I don't think that's gone anywhere. That would 
allow the extensive patches in the anaconda matplotlib recipe (and 
probably many other recipes for C and Unixy packages) to go away. (Note 
that the "pkgconfig" Python package in Anaconda is just the Python 
wrapper to the underlying Unix tool which is not present in Anaconda).
Mike
On 07/22/2015 07:52 PM, Nathan Goldbaum wrote:
> One way to do this is to build a Conda package using the matplotlib 
> recipe:
>
> https://github.com/conda/conda-recipes/tree/master/matplotlib
>
> Looking at the Conda recipe might give you some hints about how it 
> locates png.h as well, although I haven't checked in detail.
>
> On Wednesday, July 22, 2015, Brian Granger <ell...@gm... 
> <mailto:ell...@gm...>> wrote:
>
> No I am fine linking against the stuff that ships with conda - just
> not clear on how to get the setup.py logic to look in the right place.
>
> On Wed, Jul 22, 2015 at 11:20 AM, Phil Elson <pel...@gm...
> <javascript:;>> wrote:
> > Are you wanting to link against anything other than that
> installed with
> > conda?
> > The output of setup.py is normally pretty helpful at letting you
> know which
> > library it has found to build against.
> >
> > On 20 July 2015 at 01:54, Brian Granger <ell...@gm...
> <javascript:;>> wrote:
> >>
> >> Hi all,
> >>
> >> I am trying to get a dev build of matplotlib working with the
> anaconda
> >> python.
> >>
> >> Any advice on getting matplotlib to detect and use any of the
> >> libpng/freetypes:
> >>
> >> * Those installed with anaconda python.
> >> * Those from homebrew
> >> * Those that ship with OS X
> >>
> >> Cheers,
> >>
> >> Brian
> >>
> >> --
> >> Brian E. Granger
> >> Cal Poly State University, San Luis Obispo
> >> @ellisonbg on Twitter and GitHub
> >> bgr...@ca... <javascript:;> and ell...@gm...
> <javascript:;>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Don't Limit Your Business. Reach for the Cloud.
> >> GigeNET's Cloud Solutions provide you with the tools and
> support that
> >> you need to offload your IT needs and focus on growing your
> business.
> >> Configured For All Businesses. Start Your Cloud Today.
> >> https://www.gigenetcloud.com/
> >> _______________________________________________
> >> Matplotlib-devel mailing list
> >> Mat...@li... <javascript:;>
> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> >
>
>
>
> --
> Brian E. Granger
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgr...@ca... <javascript:;> and ell...@gm...
> <javascript:;>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li... <javascript:;>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

nabble is also another fairly commonly used resource for viewing archived
discussions.
On Fri, Jul 31, 2015 at 2:14 PM, Jouni K. Seppänen <jk...@ik...> wrote:
> Neal Becker <ndb...@gm...> writes:
>
> > I read via gmane: I guess this will need to be updated?
>
> I attempted to send a message to gmane.discuss to request this, but it
> seems there is some problem with that mailing list - the latest message
> is from July 17 when viewed via NNTP, and usually there are at several
> messages per week. I have emailed the gmane.org administrator to ask
> about the status.
>
> --
> Jouni K. Seppänen
> http://www.iki.fi/jks
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Neal Becker <ndb...@gm...> writes:
> I read via gmane: I guess this will need to be updated?
I attempted to send a message to gmane.discuss to request this, but it
seems there is some problem with that mailing list - the latest message
is from July 17 when viewed via NNTP, and usually there are at several
messages per week. I have emailed the gmane.org administrator to ask
about the status.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

I read via gmane: I guess this will need to be updated?

Due to recent technical problems and changes in policy on SourceForge, 
we have decided to move the matplotlib mailing lists to python.org.
To subscribe to the new mailing lists, please visit:
 *
 For user questions and support:
 https://mail.python.org/mailman/listinfo/matplotlib-users
 mat...@py...
 *
 For low-volume announcements about matplotlib releases and related
 events and software:
 https://mail.python.org/mailman/listinfo/matplotlib-announce
 mat...@py...
 *
 For developer discussion:
 https://mail.python.org/mailman/listinfo/matplotlib-devel
 mat...@py...
The old list will remain active in the meantime, but all new posts will 
auto-reply with the location of the new mailing lists.
The old mailing list archives will remain available.
Thanks to Ralf Hildebrandt at python.org for making this possible.
Cheers,
Michael Droettboom
​

One of my co-workers brought this to my attention:
http://savvastjortjoglou.com/nba-shot-sharts.html
Tom

Thomas Caswell <tca...@gm...>
writes:
> The general approach follows R / seaborn / panadas and allows users to pass
> in a `data` kwarg which if present, any data fields which are strings are
> replaced by a call to `data[key]`. In code
>
> ax.plot(labeled_data['a'], labeled_data['b'])
>
> and
>
> ax.plot('a', 'b', data=labeled_data)
>
> are equivalent.
I commented on github briefly, but here's an expanded argument. I'm
proposing that instead of using strings (or only strings) as labels, we
allow arbitrary (hashable) objects to be looked up from the data dict.
I think using strings, or at least restricting to strings only is a
mistake for two reasons. One reason has been touched upon: in
 ax.scatter('a', 'b', c='b', data=data)
should c='b' be interpreted as a constant blue color or a sequence to be
looked up from data['b']?
Another is that since this functionality seems to be modeled after R's
plot functions, people will want to do more than just lookups. A simple
labeled plot in R is
 plot(speed ~ dist, data=cars)
but you can also do expressions, e.g.
 plot(speed^2 ~ dist, data=cars)
if you want to plot the square of speed against dist. This is pretty
neat for trying to find transformations for variables that depend on
each other non-linearly.
If we only allow strings as placeholders for plottable variables,
implementing expressions gets pretty clunky. We'd basically end up
defining a mini-language for parsing expressions from strings. But if
we allow objects for which you can implement methods like __add__,
it's much nicer. There's sample code below.
I'm proposing a small change to the patch. This still allows using
strings but also user-defined objects:
https://github.com/jkseppan/matplotlib/commit/b4709b38426ad5c2905f3ce253ce1bb68d314e7e
Here's a demo of implementing expressions on top of that patch:
https://github.com/jkseppan/matplotlib/blob/label-with-nonstrings/lib/matplotlib/tests/test_labeled.py
Here's how the test case looks, and the (albeit incomplete) expression
classes and evaluator to support this are about 50 lines of pretty simple
code.
 def test_expression_of_labels():
 fig, axes = plt.subplots(2, 2)
 x, y, z = Expr.vars('x y z')
 data = {'x': np.arange(10),
 'y': np.array([3, 1, 4, 1, 5, 9, 2, 6, 5, 3]),
 'z': np.array([2, 7, 1, 8, 2, 8, 1, 8, 2, 8])}
 ev = Evaluator(data)
 axes[0, 0].plot(x, y, data=ev)
 axes[0, 1].plot(x, 2 * y + 1, data=ev)
 axes[1, 0].plot(x, y ** 2, data=ev)
 axes[1, 1].plot(x, 2 * y ** z, data=ev)
The output:
https://raw.githubusercontent.com/jkseppan/matplotlib/label-with-nonstrings/lib/matplotlib/tests/baseline_images/test_labeled/expression_of_labels.png

A couple immediate thoughts: what if the data is spread across a mix of
objects? Also, I think "labeled" might be a better kwarg name. Less likely
to conflict with apis. I'll give this a careful look-see tomorrow.
Ben Root
On Jul 25, 2015 7:03 PM, "Thomas Caswell" <tca...@gm...> wrote:
> Hey all,
>
> Everyone should be aware of
> https://github.com/matplotlib/matplotlib/pull/4787 which is both a very
> simple, but very important change to the mpl API by providing a minimal API
> to pass labeled data (that is anything that `foo[key]` return an array-like
> object) into mpl plotting functions.
>
> This is due to Fernando and Brian's persuasive case to the importance of
> starting to address labeled data in mpl and it is now or in 6-9 months
>
> The general approach follows R / seaborn / panadas and allows users to
> pass in a `data` kwarg which if present, any data fields which are strings
> are replaced by a call to `data[key]`. In code
>
> ax.plot(labeled_data['a'], labeled_data['b'])
>
> and
>
> ax.plot('a', 'b', data=labeled_data)
>
> are equivalent.
>
> This is the minimal change to get quality of life for users who work with
> labeled data at the repl and to put a flag in the sand for the API that
> down stream projects should be targeting.
>
> Major changes to what the plotting functions do (inferring labels,
> inferring what computation to do etc) are out of scope for _this_ PR which
> I want to see included in 1.5. What a higher-level API which can make use
> of the additional meta-data available looks like is a much larger
> discussion which will must have input from all of the stake holders (ex
> IPython, pandas, bokeh, seaborn, xray).
>
> Tom
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>