Re: [matplotlib-devel] Reorganizing axes plot methods

2013-07-17 Thread Michael Droettboom 

Yes.  This is great work!

Just to chime in (after having been away for most of this conversation) -->

I think we can do this reorganization now without introducing any 
implicit (or otherwise) use of gca()/pyplot stuff in the Axes class 
methods.  Refactoring how the pyplot wrapper is done can be done as a 
separate project at a later time (or even in parallel if someone wants 
to, since all of Nelle's work at the end of the day doesn't change the 
Axes interface).


My only other comment (and I mentioned this in PR #2213 as well) is that 
having the short stub functions in the Axes class in addition to the 
actual implementations elsewhere introduces a new 
synchronization/maintenance problem between the two.  Maybe it makes 
sense to merely add the implementation functions to the Axes class 
namespace dynamically.  Magical, sure, but should have ultimately the 
same result as far as introspection, autocompletion and other IPython 
goodness is concerned.


Mike

On 07/11/2013 11:47 PM, Tony Yu wrote:

Nelle, this is great! Thanks for getting the ball rolling!

Cheers,
-Tony


On Thu, Jul 11, 2013 at 6:31 AM, Nelle Varoquaux 
mailto:[email protected]>> wrote:


FYI, I have started the refactoring we discussed at scipy. I think
what tony is suggesting is the same thing.

I've created a "work in progress" pull request:
https://github.com/matplotlib/matplotlib/pull/2213

In the refactoring we discussed at Scipy, we did not mention the
pyplots wrapper at all. It does not impact pyplot or the axes module
at all as it doesn't change the API at all. If we want to do something
more in depth that impacts the API, I think it would be worth writing
a MEP.

Thanks,
N


On 11 July 2013 13:12, Anton Akhmerov mailto:[email protected]>> wrote:
> Eric Firing  writes:
>>
>> Anton,
>>
>> Yes, I have done things like that in my own code, and basemap has a
>> similar ability to call gca() when an Axes is not supplied.
 One can
>> even perform the pyplot import on an as-needed basis instead of
raising
>> an error. Nevetheless, it still represents what I view as a big
change
>> in mpl design, scrambling the state machine pyplot layer into
the OO
>> layer.  Sometimes this sort of thing is good, sometimes it
isn't.  In
>> the present case, I am far from convinced that it would be good.  I
>> don't see any real benefit at all over the present design.  I
think that
>> for the sanity of the developers, if nothing else, it is
important to
>> maintain some clear layering and hierarchy.
>>
>> Eric
>>
>
> I completely agree with that, and I just wanted to point out the
possibility.
> With the proposed separation of the plots to a separate module,
I think, the
> reasonable thing for pyplot would be to wrap the corresponding
plot functions
> by feeding gca into the axis argument.
>
> PS for what I think, pyplot right now is way too thick of a layer,
> obstructing an API use of backends.
>
> Anton
>
>
>

--
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from
AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
>
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> ___
> Matplotlib-devel mailing list
> [email protected]

> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Matplotlib-devel mailing list
[email protected]

https://lists.sourceforge.net/lists/listinfo/matplotlib-devel




--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk


___
Matplotlib-devel mailing list
Matplotlib-

[matplotlib-devel] MEP19: Continuous Integration

2013-07-17 Thread Michael Droettboom 
I've started a MEP related to improving our continuous integration 
system for matplotlib.


https://github.com/matplotlib/matplotlib/wiki/Mep19

Rather than deal to much with implementation at this point, I thought it 
best to start by outlining our requirements.  At this point, let's just 
get everything we'd like in, and we can worry about prioritizing things 
later.


Once that's done, we can start discussing how to get things set up. We 
have some donation money to use for buying machines or paying for 
services, so we are not limited to what is available for free.  I would 
particularly like feedback from others who have set up similar things.  
I have some experience with ShiningPanda (a service based on Jenkins), 
and Travis.  We used buildbot in the past, but I have little direct 
experience with it.  Are there other obvious candidates or approaches?


Mike
--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] Reorganizing axes plot methods

2013-07-17 Thread Eric Firing 
On 2013/07/17 3:14 AM, Michael Droettboom wrote:
> Yes.  This is great work!
>
> Just to chime in (after having been away for most of this conversation) -->
>
> I think we can do this reorganization now without introducing any
> implicit (or otherwise) use of gca()/pyplot stuff in the Axes class
> methods.  Refactoring how the pyplot wrapper is done can be done as a
> separate project at a later time (or even in parallel if someone wants
> to, since all of Nelle's work at the end of the day doesn't change the
> Axes interface).
>
> My only other comment (and I mentioned this in PR #2213 as well) is that
> having the short stub functions in the Axes class in addition to the
> actual implementations elsewhere introduces a new
> synchronization/maintenance problem between the two.  Maybe it makes
> sense to merely add the implementation functions to the Axes class
> namespace dynamically.  Magical, sure, but should have ultimately the
> same result as far as introspection, autocompletion and other IPython
> goodness is concerned.
>
> Mike

Mike,

One other option is to have the new private modules include mixin 
classes from which Axes would inherit methods.  There would be a lot of 
mixins, and this would be an example of the dreaded multiple 
inheritance, but it would be simple and explicit, with no magic.

Eric


--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

[matplotlib-devel] closing (and opening) the user survey?

2013-07-17 Thread Paul Ivanov 
Hey everyone,

I hope this email finds you well. I got a request today from
someone wanting to look at the survey results. How do you feel
about just sharing the full document? We're at 580 responses
right now, and it's been really a slow trickle in last couple of
weeks after the initial splash. Or we could do another round on
twitter and G+ and say the survey will be closed at the end of
the month, and then release the results.

Thoughts?

best,
-- 
   _
  / \
A*   \^   -
 ,./   _.`\\ / \
/ ,--.S\/   \
   /  `"~,_ \\
 __o   ?
   _ \<,_ /:\
--(_)/-(_).../ | \
--...J
Paul Ivanov
http://pirsquared.org

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] closing (and opening) the user survey?

2013-07-17 Thread HadiM 
It was me :-)

Only a day to day user who follow matplotlib (and other famous libs)
development. I clicked on the survey thinking it was public. Anyway it was
only curiosity so if you prefer keep it secret, it's cool for me !

Keep the good work guys !!!


--
HadiM


On Thu, Jul 18, 2013 at 12:12 AM, Paul Ivanov  wrote:

> Hey everyone,
>
> I hope this email finds you well. I got a request today from
> someone wanting to look at the survey results. How do you feel
> about just sharing the full document? We're at 580 responses
> right now, and it's been really a slow trickle in last couple of
> weeks after the initial splash. Or we could do another round on
> twitter and G+ and say the survey will be closed at the end of
> the month, and then release the results.
>
> Thoughts?
>
> best,
> --
>_
>   / \
> A*   \^   -
>  ,./   _.`\\ / \
> / ,--.S\/   \
>/  `"~,_ \\
>  __o   ?
>_ \<,_ /:\
> --(_)/-(_).../ | \
> --...J
> Paul Ivanov
> http://pirsquared.org
>
>
> --
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> ___
> Matplotlib-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk___
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel