On Fri, Oct 25, 2013 at 3:32 PM, Todd toddr...@gmail.com wrote:
I think one thing that contributes a lot to the API issues is the
inconsistency between pyplot API and the OO API. There isn't any reason
the APIs need to be so different.
indeed.
I hadn't even realized how different they
On 10/25/2013 06:42 PM, Todd wrote:
I think another problem is having pyplot and axes as dumping grounds
for all plot types. This probably made sense back when there were
only a few types of plots, but now there is a massive number of them.
They all end up in one large class with one large
On 24/10/2013 21:26, Paul Ivanov wrote:
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
Daniele,
On Fri, Oct 25, 2013 at 8:45 AM, Daniele Nicolodi dani...@grinta.netwrote:
On 24/10/2013 21:26, Paul Ivanov wrote:
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 =
There needs to be layers to the interface. At the bottom there is super
general stuff that will cover (we hope) 100% of use cases. However, the
cost is a very verbose interface with lots of knobs. To cope with this
there are higher level function which can deal with 90% of the use cases
and do
On Oct 24, 2013 8:40 PM, Chris Barker chris.bar...@noaa.gov wrote:
On Thu, Oct 24, 2013 at 8:29 AM, Michael Droettboom md...@stsci.edu
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
On Fri, Oct 25, 2013 at 6:34 AM, Benjamin Root ben.r...@ou.edu wrote:
It doesn't feel weird. It feels generalized.
or both ;-)
It is the same way to add any number of plots, regardless if it is just
one, or twenty. If you don't want to do it that way, you can just simply do:
fig =
I think one thing that contributes a lot to the API issues is the
inconsistency between pyplot API and the OO API. There isn't any reason
the APIs need to be so different.
To continue with this example, pyplot.subplot and Figure.add_subplot do
basically the same thing, but they have different
I think another problem is having pyplot and axes as dumping grounds for
all plot types. This probably made sense back when there were only a few
types of plots, but now there is a massive number of them. They all end up
in one large class with one large documentation page, making it very hard
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
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...@stsci.edu wrote:
Just a reminder, we are having a general matplotlib development hangout
today. Everyone that responded to the
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,
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
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,
On Thu, Oct 24, 2013 at 8:29 AM, Michael Droettboom md...@stsci.edu 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
On 24/10/2013 20:39, Chris Barker wrote:
On Thu, Oct 24, 2013 at 8:29 AM, Michael Droettboom md...@stsci.edu 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.
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
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_embeddedv=hWA6dMiSUiU
best,
--
_
/ \
18 matches
Mail list logo
