matplotlib-devel Mailing List for matplotlib

On Thu, Oct 24, 2013 at 12:03 PM, Daniele Nicolodi <da...@gr...> wrote:
> PS: Chris, would you mind sharing the material you put together and
> links to material from which you stole from? Thanks!
I honestly don't think my stuff is any better than the originals: I like these:
Ben Root's Scipy Tutorial -- really nice, Ben!
 https://github.com/WeatherGod/AnatomyOfMatplotlib
>From the software carpentry site:
 https://github.com/swcarpentry/bc/tree/gh-pages/lessons/thw-matplotlib
(apparently originally from Katy and Antony)
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

Michael Droettboom, on 2013年10月24日 09:41, wrote:
> I'll post a public URL to watch along once it begins as well.
Here's the youtube video link (which I got from Mike's G+):
https://www.youtube.com/watch?feature=player_embedded&v=hWA6dMiSUiU
best,
-- 
 _
 / \
 A* \^ -
 ,./ _.`\\ / \
 / ,--.S \/ \
 / `"~,_ \ \
 __o ?
 _ \<,_ /:\
--(_)/-(_)----.../ | \
--------------.......J
Paul Ivanov
http://pirsquared.org

One quick reply:
Daniele Nicolodi, on 2013年10月24日 21:03, wrote:
> One thing I dislike is, for example, the add_subplot() method:
> 
> f = plt.figure()
> a = f.add_subplot(111)
> a.plot(x, y)
>
> it feels completely out of place (why I need to add a subplot if the
> only thing I want to do is to create a figure with a single plot in it?)
> and kind of magic (what is the number 111?).
 
 f, a = plt.subplots()
 a.plot(x, y)
that's the way to go there. And if you need to make a regular
grid of subplots, you can pass it the number of rows and number
of columns, and get a 2D array of subplots out for the second
argument.
 f, axes = plt.subplots(2,3)
 axes[0,2].plot(range(10))
 axes[1,1].plot(-np.arange(10))
 f.canvas.draw()
best,
-- 
 _
 / \
 A* \^ -
 ,./ _.`\\ / \
 / ,--.S \/ \
 / `"~,_ \ \
 __o ?
 _ \<,_ /:\
--(_)/-(_)----.../ | \
--------------.......J
Paul Ivanov
http://pirsquared.org

On 24/10/2013 20:39, Chris Barker wrote:
> On Thu, Oct 24, 2013 at 8:29 AM, Michael Droettboom <md...@st...> wrote:
>> Here are the notes with action items from the meeting:
> 
> thanks for posting that. I see:
> 
> pylab - should it stay or should it go?
> 
> Comment from the peanut gallery:
> 
> Go.
> 
> But beyond that, matplotlib.pyplot is a big mess of both the
> matlab-style state-machine current figure, current axis stuff, and
> what you need to do (at least reasonably on the command line) OO
> interface.
> 
> This makes it really hard to teach to newbies -- I just did this last
> night, and made a point to use tutorials that emphasize the OO
> interface (Thanks Ben Root, Katy Huff, and Antony Scopatz, and I'm
> sure others that helped put the materials together that I stole
> from...). However, there were still a number of examples in there that
> just called "plot()" or whatever, and even if there were not, the
> namespace is really cluttered with stuff!
> 
> Anyone like the idea of an matplotlib.ooplot namespace that would have
> just what you need to use the oo style?
Hello,
I agree that the matlab like API should be at least discouraged, however
I think there are some shortcomings both in the documentation and
examples and in the object oriented API and functions exposed through
the pyplot namespace that make switching more cumbersome that it has to bee.
One thing I dislike is, for example, the add_subplot() method:
f = plt.figure()
a = f.add_subplot(111)
a.plot(x, y)
it feels completely out of place (why I need to add a subplot if the
only thing I want to do is to create a figure with a single plot in it?)
and kind of magic (what is the number 111?).
The API is also very old fashion python (getter and setter methods for
example) and many methods try to emulate too much of the bad API design
of matlab (doing completely different things depending on the kind and
number of parameters).
I believe it would be possible to come up with a more modern and lean
API that would be easier and nicer to use. If we have to deprecate the
matlab style API, maybe it would be worth to replace it with something
substantially better.
PS: Chris, would you mind sharing the material you put together and
links to material from which you stole from? Thanks!
Cheers,
Daniele

On Thu, Oct 24, 2013 at 8:29 AM, Michael Droettboom <md...@st...> wrote:
> Here are the notes with action items from the meeting:
thanks for posting that. I see:
pylab - should it stay or should it go?
Comment from the peanut gallery:
Go.
But beyond that, matplotlib.pyplot is a big mess of both the
matlab-style state-machine current figure, current axis stuff, and
what you need to do (at least reasonably on the command line) OO
interface.
This makes it really hard to teach to newbies -- I just did this last
night, and made a point to use tutorials that emphasize the OO
interface (Thanks Ben Root, Katy Huff, and Antony Scopatz, and I'm
sure others that helped put the materials together that I stole
from...). However, there were still a number of examples in there that
just called "plot()" or whatever, and even if there were not, the
namespace is really cluttered with stuff!
Anyone like the idea of an matplotlib.ooplot namespace that would have
just what you need to use the oo style?
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

Three weeks time... see you all there!
(I've also added it to the matplotlib Google Calendar here: 
https://www.google.com/calendar/feeds/79hk8jhvlks8jn8ds4ri1e6q4g%40group.calendar.google.com/public/basic)
Mike
-- 
 _
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com

Here are the questions I asked during the hangouts session (paraphrased):
-------------------------------------------------------------
Regarding continuous integration:
Has looked into OBS? (open build server, https://build.opensuse.org/) It
can be installed on a local machine or server, supports automatically
creating and deleting fresh images with each build, and supposedly works
with osX as well as Linux although I haven't tested it (it does need a Mac
OsX VM).
-------------------------------------------------------------
Regarding bug handling:
It might be possible to do something with this with Google Code-in (
https://developers.google.com/open-source/gci/), although I am not 100%
sure this would be acceptable there.
Another possibility would be to allow volunteer triagers who may not be
developers but can at least handle basic stuff like finding duplicates and
following up with the reporters of old bugs.
-------------------------------------------------------------
Regarding embedding:
Perhaps there could be a generic "figure" widget for each backend. The
widget would automatically handle all the backend-specific stuff necessary
to create a figure object and display it in the widget (including resizing
and such). It would provide access to the low-level backend-specific parts
to make it possible to subclass it or change the details of how it works.
The figure windows would have this widget as their central widget, and
would probably access it using these low-level components.
However, for basic usage each widget would also have a "figure" attribute,
which would contain a single generic figure object. Basic users who just
want to embed a regular plot could access that figure object and use it in
the normal way.
These could probably all be accessed from a single module, although they
probably would all live in their own backend-specific modules.
It wouldn't allow people to use pyplot, but if this was the documented way
to do embedding and the documentation made it clear you needed to use the
OO interface when embedding I think it would greatly reduce the amount of
trouble people have.

Hi,
For the CI stuff, I think it would be worth discussing this with the
Enthought guys, specifically Didrik Pinte and David Cournapeau.
>From what I understood, they are developping some stuff to
automatically build canopy from projects hosted on github. Hence, they
have to run all the tests, on different plateforms, and they are OK
with chatting with some of us.
Cheers,
N
On 24 October 2013 17:29, Michael Droettboom <md...@st...> wrote:
> Here are the notes with action items from the meeting:
>
> https://docs.google.com/document/d/1nVM9qDooU5nX6WSKWPTYd2kN6wBxqOWZZTNOM1k0FdA/edit?usp=sharing
>
> Sorry about not seeing questions posted from non-participants. I'll try
> to work out that kink for next time.
>
> Mike
>
> On 10/24/2013 09:41 AM, Michael Droettboom wrote:
>> Just a reminder, we are having a general matplotlib development hangout
>> today. Everyone that responded to the Doodle poll from a few weeks ago
>> will get an invite, along with Matthew Terry and Matthew Brett if they
>> can make it to discuss their work with testing and builds.
>>
>> We have a few extra spots, so let me know if you'd like an invite (first
>> come, first served).
>>
>> I'll post a public URL to watch along once it begins as well.
>>
>> Mike
>>
>
>
> --
> _
> |\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
> | ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
>
> http://www.droettboom.com
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Here are the notes with action items from the meeting:
https://docs.google.com/document/d/1nVM9qDooU5nX6WSKWPTYd2kN6wBxqOWZZTNOM1k0FdA/edit?usp=sharing
Sorry about not seeing questions posted from non-participants. I'll try 
to work out that kink for next time.
Mike
On 10/24/2013 09:41 AM, Michael Droettboom wrote:
> Just a reminder, we are having a general matplotlib development hangout
> today. Everyone that responded to the Doodle poll from a few weeks ago
> will get an invite, along with Matthew Terry and Matthew Brett if they
> can make it to discuss their work with testing and builds.
>
> We have a few extra spots, so let me know if you'd like an invite (first
> come, first served).
>
> I'll post a public URL to watch along once it begins as well.
>
> Mike
>
-- 
 _
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com

Was anyone looking at the questions? I posted a bunch of questions but
nobody seemed to notice them.
On Thu, Oct 24, 2013 at 3:41 PM, Michael Droettboom <md...@st...> wrote:
> Just a reminder, we are having a general matplotlib development hangout
> today. Everyone that responded to the Doodle poll from a few weeks ago
> will get an invite, along with Matthew Terry and Matthew Brett if they
> can make it to discuss their work with testing and builds.
>
> We have a few extra spots, so let me know if you'd like an invite (first
> come, first served).
>
> I'll post a public URL to watch along once it begins as well.
>
> Mike
>
> --
> _
> |\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
> | ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
>
> http://www.droettboom.com
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Just a reminder, we are having a general matplotlib development hangout 
today. Everyone that responded to the Doodle poll from a few weeks ago 
will get an invite, along with Matthew Terry and Matthew Brett if they 
can make it to discuss their work with testing and builds.
We have a few extra spots, so let me know if you'd like an invite (first 
come, first served).
I'll post a public URL to watch along once it begins as well.
Mike
-- 
 _
|\/|o _|_ _. _ | | \.__ __|__|_|_ _ _ ._ _
| ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |
http://www.droettboom.com